| 1 |
good point, but you can be smart about it and try and test where you get |
| 2 |
the most bang for your buck. for example, set all possible USE flags for |
| 3 |
a build and test the latest stable release. sure, you're missing some |
| 4 |
cases, but you're (hopefully) hitting the common ones. |
| 5 |
|
| 6 |
in truth, my autobuilder is going to be used to automate building of |
| 7 |
packages that aren't already keyworded for a give ARCH. it just happens |
| 8 |
that it can be used for what riyad suggests too. |
| 9 |
|
| 10 |
nall. |
| 11 |
|
| 12 |
On Wed, 2002-12-11 at 11:28, Brian Magnuson wrote: |
| 13 |
> This is a nice idea, but I think that the problem becomes intractable when you |
| 14 |
> take USE flags into account. To properly test an ebuild you would have to build |
| 15 |
> it with every permutation of it USE flags. As an extreme example, mplayer takes |
| 16 |
> something like 20 possible USE flags. That's about 1000000 builds of mplayer |
| 17 |
> that you just signed up for. Or 32 seperate builds of xfree86, and that's for |
| 18 |
> every version that current exists in portage, not just the latest one. You can |
| 19 |
> see how this gets out of control rather quickly... |
| 20 |
> |
| 21 |
> |
| 22 |
> * Riyad Kalla <rsk@×××××××××.edu> [2002-12-11 09:45]: |
| 23 |
> > Does Gentoo have a script that can test all available emerges for |
| 24 |
> > errors? Say have a machine setup, that has fast compiler settings (no |
| 25 |
> > optimizations) that just emerges the entire portage tree all day long... |
| 26 |
> > or do you just wait for people to report problems when emerging |
| 27 |
> > packages? |
| 28 |
> > |
| 29 |
> > is there anywya to automate this task? Seems not very likely, but I'm |
| 30 |
> > not sure of the intracacies of portage... |
| 31 |
> > |
| 32 |
> > -Riyad |
| 33 |
> > |
| 34 |
> > |
| 35 |
> > -- |
| 36 |
> > gentoo-dev@g.o mailing list |
| 37 |
> > |
| 38 |
> |
| 39 |
> -- |
| 40 |
> gentoo-dev@g.o mailing list |
| 41 |
> |
Archives