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