| 1 |
I started making a C++ app using Qt but it's a command line app and |
| 2 |
outputs into a text file. Well it's a little more daunting then I |
| 3 |
expected :P but so far I have it iterating through the directories of |
| 4 |
/usr/portage and listing sub-directories in each category. Unless |
| 5 |
someone finishes this solution before me I'm going to contiune and code |
| 6 |
the portion that filters out all the *.ebuild files and searches within |
| 7 |
them for 'ppc' and '~ppc' keywords then compile a full list of which |
| 8 |
ebuilds have which keyword, all outputted into a text file. |
| 9 |
Now to get some sleep and be ready for work tommarow. |
| 10 |
|
| 11 |
Thanh Ly |
| 12 |
|
| 13 |
P.S. |
| 14 |
I'm a C++ junkie, if this can be done easier in a scripting language, |
| 15 |
great, maybe someone else will come up with the script. |
| 16 |
|
| 17 |
On Tue, 2003-09-02 at 23:28, David Holm wrote: |
| 18 |
> Hello, |
| 19 |
> I had an idea. Since there are a number of ebuilds in portage that are only marked x86 or ~x86 |
| 20 |
> but would work just as well (better =) on ppc someone should write a script to find these |
| 21 |
> ebuilds and compile a list. |
| 22 |
> We could then post it on the webpage and urge users to help us test packages. |
| 23 |
> |
| 24 |
> If I was a better scripter I would have written something myself but I believe someone else |
| 25 |
> would be able to do a much better job of it in less time than I would. |
| 26 |
> |
| 27 |
> //David Holm |
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-ppc-dev@g.o mailing list |
Archives