On Sun, Feb 03, 2013 at 12:50:02AM +0100, Michał Górny wrote: > On Sat, 2 Feb 2013 23:33:26 +0000 > "Aaron W. Swenson" <[email protected]> wrote: > > > After years of "if use test ; then ..." just working when > > FEATURES="test" is declared, it isn't working with EAPI5. > > You shouldn't admit that for years you didn't knew that this was > incorrect and you should have been using IUSE=test.
Let me rephrase that: Experience led me to 'FEATURE="test"' implies 'USE="test"' regardless of whether "test" is in IUSE or not. Further, if I'm adding FEATURE="test", why wouldn't I also want USE="test". > > I think we could save some bytes and headaches if we just add "test" > > to IUSE_IMPLICIT. > > First of all, you should note that you will still need to add IUSE=test > to pre-EAPI 5 ebuilds. Not need. Apparently supposed to have done that, though. As I said, it has been working without it for years and only stopped when I used EAPI5. > Secondly, what about all the ebuilds which declare IUSE=test in EAPI 5? > Shall we remove that value from IUSE? Keep it? > "test" being in IUSE becomes moot. It wouldn't much matter whether it's there or it isn't. > What will be the impact on metadata? It seems that the PMS allows > dependencies on IUSE_EFFECTIVE, so we can basically have dependencies > with flags which are valid only on some of the profiles... IUSE_EFFECTIVE is probably better. -- Mr. Aaron W. Swenson Gentoo Linux Developer Email : [email protected] GnuPG FP : 2C00 7719 4F85 FB07 A49C 0E31 5713 AA03 D1BB FDA0 GnuPG ID : D1BBFDA0
signature.asc
Description: Digital signature
