| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ciaran McCreesh wrote: |
| 5 |
> On Mon, 09 Mar 2009 13:56:19 -0700 |
| 6 |
> Zac Medico <zmedico@g.o> wrote: |
| 7 |
>> Ciaran McCreesh wrote: |
| 8 |
>>> * Limit values in $USE to ones in $IUSE (bug 176467). The existing |
| 9 |
>>> behaviour's majorly annoying; time for the package manager to |
| 10 |
>>> start enforcing things strictly. |
| 11 |
>> My impression is that most ebuild developers tend to dislike the |
| 12 |
>> idea of adding profile-specific flags such as $ARCH, userland_*, |
| 13 |
>> kernel_*, and elibc_* to IUSE. Perhaps there should be exemptions |
| 14 |
>> for these? |
| 15 |
> |
| 16 |
> If we must do that... Can we get something in profiles a bit like this: |
| 17 |
> |
| 18 |
> USE_EXPAND_IMPLICIT="USERLAND KERNEL ELIBC ARCH" |
| 19 |
> USE_EXPAND_UNPREFIXED="ARCH" |
| 20 |
> USE_EXPAND_VALUES_USERLAND="GNU freebsd" |
| 21 |
> USE_EXPAND_VALUES_KERNEL="linux blah" |
| 22 |
> USE_EXPAND_VALUES_ELIBC="glibc" |
| 23 |
> USE_EXPAND_VALUES_ARCH="x86 amd64 sparc mips blah" |
| 24 |
> |
| 25 |
> so we've got an enforcable complete list of every legal value for |
| 26 |
> them, and less associated mess? |
| 27 |
|
| 28 |
That seems like a reasonable approach. What about flags that are |
| 29 |
commonly forced or masked such as selinux or multilib? Should there |
| 30 |
be an implicit exemption for all forced/masked flags, or should we |
| 31 |
introduce an IMPLICIT_IUSE profile variable to enumerate specific |
| 32 |
ones which are implicit members of IUSE? |
| 33 |
- -- |
| 34 |
Thanks, |
| 35 |
Zac |
| 36 |
-----BEGIN PGP SIGNATURE----- |
| 37 |
Version: GnuPG v2.0.10 (GNU/Linux) |
| 38 |
|
| 39 |
iEYEARECAAYFAkm1ig8ACgkQ/ejvha5XGaMpxwCgqi0Ma+Wv9s0coMYtagWR8Je/ |
| 40 |
hBEAn3awatpk505DxKrGtYDwTSYgn+nZ |
| 41 |
=XHzp |
| 42 |
-----END PGP SIGNATURE----- |
Archives