-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zac Medico wrote:
> Jeremy Olexa wrote:
>> So, my recommendation is to:
>> 1) mask the prefix USE flag in base/use.mask because no one except the
>> prefix profiles should use this flag.
>> 2) unmask and force the USE flag in prefix profile.
>> 3) add entry to use.desc.
>> addendum) use.{mask,force} imply that the USE flag is explicit so
>> there will be no QA warnings.
>
>> However, we have toyed with other ideas. One of which is to introduce
>> IUSE=prefix in prefix.eclass similar to the USE=multilib approach. I
>> don't really like this idea because it exposes the use flag and we
>> don't want it exposed to the users.
>
> Note that there are some changes in this area planned for EAPI 3.
> Install app-doc/pms-99999999 with USE=eapi3-draft and see section
> 4.3.2 which says that there will be a new USE_EXPAND_UNPREFIXED
> variable which you can use (it's only coincidental that your flag
> happens to be called 'prefix' and the new variable contains PREFIX
> in its name). It also says you'll be able to add your flag to
> USE_EXPAND_HIDDEN so that it's not exposed to users.
Actually, after further inspection of PMS, it seems that the
IUSE_IMPLICIT is more appropriate for the 'prefix' flag since it
doesn't seem to fit into the USE_EXPAND paradigm.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAknXsucACgkQ/ejvha5XGaO5KACg2Ay3wM5joo4tr2mAuShFBXSm
tWwAoMrpEhrBIou8fO5fGPR0AN7G89LT
=Iw82
-----END PGP SIGNATURE-----
