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