| 1 |
hmmm, meant to reply to the list. |
| 2 |
|
| 3 |
nall, who has to remember "reply all" for this list... |
| 4 |
|
| 5 |
|
| 6 |
-----Forwarded Message----- |
| 7 |
|
| 8 |
From: Jon Nall <nall@g.o> |
| 9 |
To: Riyad Kalla <rsk@×××××××××.edu> |
| 10 |
Subject: Re: [gentoo-dev] emerge test... |
| 11 |
Date: 11 Dec 2002 09:14:32 -0600 |
| 12 |
|
| 13 |
|
| 14 |
i have a script that does just this. i'm still testing it, but hope to |
| 15 |
have something in a couple of weeks (i'm also waiting on some hardware |
| 16 |
that's going to be a dedicated build machine). |
| 17 |
|
| 18 |
nall. |
| 19 |
|
| 20 |
On Wed, 2002-12-11 at 08:35, Riyad Kalla wrote: |
| 21 |
> Does Gentoo have a script that can test all available emerges for |
| 22 |
> errors? Say have a machine setup, that has fast compiler settings (no |
| 23 |
> optimizations) that just emerges the entire portage tree all day long... |
| 24 |
> or do you just wait for people to report problems when emerging |
| 25 |
> packages? |
| 26 |
> |
| 27 |
> is there anywya to automate this task? Seems not very likely, but I'm |
| 28 |
> not sure of the intracacies of portage... |
| 29 |
> |
| 30 |
> -Riyad |
| 31 |
> |
| 32 |
> |
| 33 |
> -- |
| 34 |
> gentoo-dev@g.o mailing list |
| 35 |
> |
Archives