On Sat, 2006-08-05 at 12:57 +0200, Kevin F. Quinn wrote: > On Sat, 5 Aug 2006 11:49:53 +0200 > Danny van Dyk <[EMAIL PROTECTED]> wrote: > > > Please re-read the list of packages that fail tests: > > * glibc > > * autoconf > > * gettext > > * tar > > That makes _4_ system packages. Before I would consider making > > FEATURES=test a default, I would add least want the system set to > > actually merge with it. > > So you're happy to let users install these packages without them > knowing the tests would fail? > > I certainly agree they should pass their tests. autoconf-2.60, > gettext-0.15 and tar-1.15.1-r1, which are the latest versions I > have installed here, all pass on my system. If they fail on your > platform, then you should make sure bugs are open and the relevant > maintainers are doing something about it, and IMO they should not go to > arch (i.e. should remain ~arch) until the test issues are resolved. > > Thing is, at the moment you have a bunch of packages installed that > fail their tests. This may mean the tests are broken, however it may > also mean the packages are not working correctly on your system, and > I'd be concerned if I were you.
With some arches this is not really an option. Also system pkgs such like the toolchain need to have additional deps. > Avoiding the test phase doesn't make > the packages work, obviously. > > glibc is somewhat of a special case; it is especially sensitive to > the environment - many of the tests assume a vanilla RedHat > environment, and often the test failures in glibc are not actual > problems with glibc but limitations of the test suite. Sometimes the tests are flat out wrong. Take for example say we decided to paxtest ran itself in as the test.. This would surely fail on amd64 as one or two of the tests assume page sizes of 4096. > However we > should not be encouraging people to install glibc versions where the > test failures are not understood. The alternative would then become for the end user to use another distro with less hassles. We would surely get the rep of sucking if nobody could even install libc. > Clearly if something in glibc is not > behaving properly, the effects can be nasty. Which for the most part is why features like this should be opt-in vs opt-out or be left up to the $ARCH teams. A lot of people are opting in so most of these will be fixed in due time.. The $ARCH teams *should* already be setting this feature for the most part before stable markings. It's a noble idea. I just don't think we are ready for FEATURES=test && USE=test either. -- Ned Ludd <[EMAIL PROTECTED]> Gentoo Linux -- gentoo-dev@gentoo.org mailing list
