| 1 |
On Sat, Aug 05, 2006 at 02:35:49PM -0400, Mike Frysinger wrote: |
| 2 |
> On Saturday 05 August 2006 06:57, Kevin F. Quinn wrote: |
| 3 |
> > On Sat, 5 Aug 2006 11:49:53 +0200 |
| 4 |
> > Danny van Dyk <kugelfang@g.o> wrote: |
| 5 |
> > > Please re-read the list of packages that fail tests: |
| 6 |
> > > * glibc |
| 7 |
> > > * autoconf |
| 8 |
> > > * gettext |
| 9 |
> > > * tar |
| 10 |
> > > That makes _4_ system packages. Before I would consider making |
| 11 |
> > > FEATURES=test a default, I would add least want the system set to |
| 12 |
> > > actually merge with it. |
| 13 |
> > |
| 14 |
> > So you're happy to let users install these packages without them |
| 15 |
> > knowing the tests would fail? |
| 16 |
> |
| 17 |
> before i added binutils-2.17, i ran `make check` on it for about 25 |
| 18 |
> targets ... of those, about 10 failed ... |
| 19 |
> |
| 20 |
> i checked with upstream and others reproduced it ... i dont know about you, |
| 21 |
> but i dont have the skills to go in and fix the failures for all of those |
| 22 |
> architectures |
| 23 |
|
| 24 |
Then RESTRICT=test, or use a src_test which warns on test failures |
| 25 |
rather than aborting, could be used. Or am I missing something? |
| 26 |
|
| 27 |
> while i like the idea of all packages being able to pass FEATURES=test, |
| 28 |
> somethings it just aint gonna happen with Gentoo's available skill set |
| 29 |
> -mike |
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives