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