| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Santiago M. Mola wrote: |
| 5 |
> On Mon, Sep 15, 2008 at 9:45 PM, Vlastimil Babka <caster@g.o> wrote: |
| 6 |
>> I think it's better to prevent this rather than waste time with bug |
| 7 |
>> reports like that. I asked Zac on IRC whether portage could filter such |
| 8 |
>> flags. He suggested using use.mask in profiles. Well since ARCH is also |
| 9 |
>> set by a profile, why not. Although a really persistent and stupid user |
| 10 |
>> could use.unmask, it's better than no protection. And then we can think |
| 11 |
>> how to replace the current ARCH->USE flag system with e.g. USE_EXPAND. |
| 12 |
>> What do you think? |
| 13 |
>> |
| 14 |
> |
| 15 |
> Seems like an acceptable workaround. |
| 16 |
> |
| 17 |
> For future EAPIs, ARCH could be a regular USE_EXPANDed flag as you |
| 18 |
> suggest, and package managers could filter any flag in USE which is |
| 19 |
> not listed in IUSE. |
| 20 |
|
| 21 |
I suspect that it may be a little more than a "workaround". Consider |
| 22 |
a case where IUSE contains elibc_glibc and the current selected |
| 23 |
profile has set ELIBC=uclibc. In this case, the user could |
| 24 |
conceivable set USE=elibc_glibc in make.conf, which would clearly be |
| 25 |
an invalid setting. Therefore, it seems natural to mask the |
| 26 |
elibc_glibc USE flag on all profiles except those which actually use |
| 27 |
glibc. |
| 28 |
|
| 29 |
- -- |
| 30 |
Thanks, |
| 31 |
Zac |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 34 |
|
| 35 |
iEYEARECAAYFAkjRHTQACgkQ/ejvha5XGaPsBwCfQ1tv/AgKH4x0PS++QtbFeav0 |
| 36 |
3NAAoJbvO3FHjt3uGL/kffOxRh7/akZq |
| 37 |
=Ez2M |
| 38 |
-----END PGP SIGNATURE----- |
Archives