[gentoo-dev] Re: Make FEATURES=test the default
Tach Hanno, 0x2B859DE3 (PGP-PK-ID) Hanno Böck schrieb: I'm all for making more use of features like test and collision-protect, though in the past I noticed that many devs don't seem to care much. I even think to remember of bugs getting closed invalid with a we don't care about-comment. But if FEATURES=test is considered more importand in the future, I'll continue bugging you with related bugs. I would also recommend all ATs not only FEATURES=collision-protect but also to activated the test suites. I normally report failing tests on all bugs I test (which are a few :), but these tests are sometimes to dependent on specific versions of other packages or the environment they nearly have no use. However I think we have a long way to go till we can even think of enabling it by default. Right. V-Li -- Fingerprint: 68C5 D381 B69A A777 6A91 E999 350A AD7C 2B85 9DE3 http://www.gnupg.org/ -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Make FEATURES=test the default
Kevin F. Quinn [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Sat, 05 Aug 2006 11:33:39 +0200: IMO devs should be working with collision-protect sandbox strict stricter test userpriv but let's not get too excited ;) Don't forget (for the appropriate arch(s)) multilib-strict! =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Make FEATURES=test the default
Kevin F. Quinn [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted below, on Sat, 05 Aug 2006 11:33:39 +0200: IMO devs should be working with collision-protect sandbox strict stricter test userpriv but let's not get too excited ;) Don't forget (for the appropriate arch(s)) multilib-strict! =8^) -- Duncan - List replies preferred. No HTML msgs. Every nonfree program has a lord, a master -- and if you use the program, he is your master. Richard Stallman -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Re: Make FEATURES=test the default
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. I have a related question, but first a comment: I like the idea, that packages run their self-tests before they get marked stable. And if it should become default and a user doesn't want it, he can disable it. So what? So my question is: where's the difference between USE=test and FEATURES=test ? So FEATURES=test means, that portage runs src_test(), right? So what does USE=test mean? signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Re: Make FEATURES=test the default
On Saturday 05 August 2006 15:14, Sven Köhler wrote: So my question is: where's the difference between USE=test and FEATURES=test ? So FEATURES=test means, that portage runs src_test(), right? So what does USE=test mean? sometimes packages require special package dependencies when the tests are run. USE=test triggers this dependencies. (look at gdb for example). regards, corsair pgpH0cXlGv3Xk.pgp Description: PGP signature
Re: [gentoo-dev] Re: Make FEATURES=test the default
On Sat, 05 Aug 2006 17:14:23 +0200 Sven Köhler [EMAIL PROTECTED] wrote: So my question is: where's the difference between USE=test and FEATURES=test ? So FEATURES=test means, that portage runs src_test(), right? Yes. So what does USE=test mean? USE=test is a workaround; portage cannot use FEATUREs in dep strings. So for example, if the test phase needs a separate tarball of data (a common enough occurrence) and the ebuild maintainer wants to download that tarball only if the tests are being run (perhaps the test data is huge), this can only be done with USE flags. Basically, if you set FEATURES=test, add test also to your USE flags. USE=test should never be used for anything other than supporting FEATURES=test. -- Kevin F. Quinn signature.asc Description: PGP signature
Re: [gentoo-dev] Re: Make FEATURES=test the default
On Sat, 5 Aug 2006 17:35:32 +0200 Kevin F. Quinn [EMAIL PROTECTED] wrote: | USE=test is a workaround; portage cannot use FEATUREs in dep | strings. Actually, it could, if anyone ever got around to adding FEATURES to USE_EXPAND... -- Ciaran McCreesh Mail: ciaran dot mccreesh at blueyonder.co.uk -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Make FEATURES=test the default
Ciaran McCreesh wrote: On Sat, 5 Aug 2006 17:35:32 +0200 Kevin F. Quinn [EMAIL PROTECTED] wrote: | USE=test is a workaround; portage cannot use FEATUREs in dep | strings. Actually, it could, if anyone ever got around to adding FEATURES to USE_EXPAND... We would do lots of things; that doesn't mean we should ;) -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Make FEATURES=test the default
On Sat, Aug 05, 2006 at 12:04:01PM -0400, Alec Warner wrote: Ciaran McCreesh wrote: On Sat, 5 Aug 2006 17:35:32 +0200 Kevin F. Quinn [EMAIL PROTECTED] wrote: | USE=test is a workaround; portage cannot use FEATUREs in dep | strings. Actually, it could, if anyone ever got around to adding FEATURES to USE_EXPAND... We would do lots of things; that doesn't mean we should ;) s/would/could/ ? Anyway, sure, there's plenty of things we could do that we shouldn't. Forcing a hack by users (USE=test) when a hack by devs is available is one such thing, in my opinion. Yes, I'm aware that relevant people think FEATURES in USE_EXPAND is a bad idea, and I'm not sure I disagree. I think as a temporary workaround until a clean fix is available, it beats the current situation, though. -- gentoo-dev@gentoo.org mailing list
