Kevin F. Quinn wrote: > I'd like to suggest we make FEATURES=test (and therefore USE=test) the > default behaviour, rather than the opt-in we currently have. Far too > many packages fail their test phase.
Sure everyone likes to watch glibc failing? :P </joke> Well, can't be done until bugs such as http://bugs.gentoo.org/show_bug.cgi?id=69343 are solved (at least as in sticking RESTRICT=test there) instead of being ignored. > At the very least, ebuild maintainers and ATs should be running with > tests switched on. If the tests are known to fail then the ebuild can > either RESTRICT=test, or just return successfully from src_test() > where the test report is useful even if some tests fail. See above. And even then, I don't think it's a good idea to force this upon users. Lots of packages have tests that are very time-consuming, and there are packages that always fail tests and it's pretty much expected (PHP is one of them; and while the failure isn't fatal there, it still takes tons of time to go thru those ~2000 tests). And there are tons of packages where tests are more or less unmaintained. -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;)
signature.asc
Description: OpenPGP digital signature
