| 1 |
I'm kind of a Gentoo n00b, though not a Linux n00b, so pardon any stupidity |
| 2 |
contained herein... ;-) |
| 3 |
|
| 4 |
Has anyone ever considered/implemented an automated build success report |
| 5 |
system? So that if I, for instance, successfully merged an ebuild w/ no ppc |
| 6 |
or ~ppc keyword, this utility could phone home and record my success. Then |
| 7 |
maybe that could automatically mark that package with a ~ppc keyword, then if |
| 8 |
enough success reports came in while it was marked ~ppc (and maybe it could |
| 9 |
be balanced against failure reports), it could automatically get marked ppc |
| 10 |
one day. |
| 11 |
|
| 12 |
The reason I ask this is that it seems that there are an awful lot of packages |
| 13 |
that don't have a ppc or ~ppc keyword, making Gentoo/PPC a lot less useful |
| 14 |
for the faint of heart (or the faint of butt) than Gentoo/x86. I was able to |
| 15 |
successfully merge koffice-1.3_rc1 on my TiBook 500, and I imagine there are |
| 16 |
plenty of other packages out there that would build successfully too, and |
| 17 |
probably have been built successfully, but not reported. I reported my |
| 18 |
success to this list, but received (as of yet) no response. It's only been a |
| 19 |
couple days, so that's not a complaint from me; I'm just trying to point out |
| 20 |
that an automated system would have already put a ~ppc keyword on this |
| 21 |
ebuild. :) |
| 22 |
|
| 23 |
Regardless of whether I have a good idea here or a terribly stupid one, I'd be |
| 24 |
really interested to learn more about the process of getting ppc and ~ppc |
| 25 |
keywords added to packages, and how I can best help increase the number of |
| 26 |
them. |
| 27 |
|
| 28 |
Thanks for a really cool distro, |
| 29 |
Wes Morgan |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-ppc-dev@g.o mailing list |
Archives