-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ciaran McCreesh wrote:
> On Mon, 09 Mar 2009 13:56:19 -0700
> Zac Medico <zmedico@g.o> wrote:
>> Ciaran McCreesh wrote:
>>> * Limit values in $USE to ones in $IUSE (bug 176467). The existing
>>>   behaviour's majorly annoying; time for the package manager to
>>> start enforcing things strictly.
>> My impression is that most ebuild developers tend to dislike the
>> idea of adding profile-specific flags such as $ARCH, userland_*,
>> kernel_*, and elibc_* to IUSE. Perhaps there should be exemptions
>> for these?
> 
> If we must do that... Can we get something in profiles a bit like this:
> 
>     USE_EXPAND_IMPLICIT="USERLAND KERNEL ELIBC ARCH"
>     USE_EXPAND_UNPREFIXED="ARCH"
>     USE_EXPAND_VALUES_USERLAND="GNU freebsd"
>     USE_EXPAND_VALUES_KERNEL="linux blah"
>     USE_EXPAND_VALUES_ELIBC="glibc"
>     USE_EXPAND_VALUES_ARCH="x86 amd64 sparc mips blah"
> 
> so we've got an enforcable complete list of every legal value for
> them, and less associated mess?

That seems like a reasonable approach. What about flags that are
commonly forced or masked such as selinux or multilib? Should there
be an implicit exemption for all forced/masked flags, or should we
introduce an IMPLICIT_IUSE profile variable to enumerate specific
ones which are implicit members of IUSE?
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)

iEYEARECAAYFAkm1ig8ACgkQ/ejvha5XGaMpxwCgqi0Ma+Wv9s0coMYtagWR8Je/
hBEAn3awatpk505DxKrGtYDwTSYgn+nZ
=XHzp
-----END PGP SIGNATURE-----