On Sat, 2 Feb 2013 23:33:26 +
"Aaron W. Swenson" wrote:
> After years of "if use test ; then ..." just working when
> FEATURES="test" is declared, it isn't working with EAPI5. I think we
> could save some bytes and headaches if we just add "test" to
> IUSE_IMPLICIT.
>
> Portage's emerge's "-
On 2013-02-02, at 6:50 PM, Michał Górny wrote:
> On Sat, 2 Feb 2013 23:33:26 +
> "Aaron W. Swenson" wrote:.
>
> First of all, you should note that you will still need to add IUSE=test
> to pre-EAPI 5 ebuilds.
>
> Secondly, what about all the ebuilds which declare IUSE=test in EAPI 5?
> S
On Sun, Feb 03, 2013 at 12:50:02AM +0100, Michał Górny wrote:
> On Sat, 2 Feb 2013 23:33:26 +
> "Aaron W. Swenson" 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 d
On Sun, 3 Feb 2013 00:50:02 +0100
Michał Górny wrote:
> 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...
I don't get it. Be more specific as to how
On Sat, 2 Feb 2013 23:33:26 +
"Aaron W. Swenson" 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.
After years of "if use test ; then ..." just working when
FEATURES="test" is declared, it isn't working with EAPI5. I think we
could save some bytes and headaches if we just add "test" to
IUSE_IMPLICIT.
Portage's emerge's "--newuse" option won't be affected by this. From
`man emerge`:
> NOTE: This
