-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Santiago M. Mola wrote: > On Mon, Sep 15, 2008 at 9:45 PM, Vlastimil Babka <[EMAIL PROTECTED]> wrote: >> I think it's better to prevent this rather than waste time with bug >> reports like that. I asked Zac on IRC whether portage could filter such >> flags. He suggested using use.mask in profiles. Well since ARCH is also >> set by a profile, why not. Although a really persistent and stupid user >> could use.unmask, it's better than no protection. And then we can think >> how to replace the current ARCH->USE flag system with e.g. USE_EXPAND. >> What do you think? >> > > Seems like an acceptable workaround. > > For future EAPIs, ARCH could be a regular USE_EXPANDed flag as you > suggest, and package managers could filter any flag in USE which is > not listed in IUSE.
I suspect that it may be a little more than a "workaround". Consider a case where IUSE contains elibc_glibc and the current selected profile has set ELIBC=uclibc. In this case, the user could conceivable set USE=elibc_glibc in make.conf, which would clearly be an invalid setting. Therefore, it seems natural to mask the elibc_glibc USE flag on all profiles except those which actually use glibc. - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkjRHTQACgkQ/ejvha5XGaPsBwCfQ1tv/AgKH4x0PS++QtbFeav0 3NAAoJbvO3FHjt3uGL/kffOxRh7/akZq =Ez2M -----END PGP SIGNATURE-----
