| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi everyone, |
| 5 |
|
| 6 |
If we mask and force various profile specific USE flags |
| 7 |
appropriately, it will give repoman the information it needs to stop |
| 8 |
producing bogus warnings about unsatisfied conditional dependencies |
| 9 |
that are actually irrelevant. An additional benefit is that emerge |
| 10 |
- --newuse will ignore the addition or removal of these flags from |
| 11 |
IUSE (since masked/forced flags do not represent choices for the user). |
| 12 |
|
| 13 |
In order to do this, selected profile specific flags should be |
| 14 |
masked in the base profile and unmasked/forced in the specific |
| 15 |
profiles which they apply to. The unmasking is necessary because |
| 16 |
use.mask currently overrides use.force. USE flags suggested as |
| 17 |
candidates for masking/forcing include all USE_EXPAND flags derived |
| 18 |
from the USERLAND, KERNEL, and ELIBC variables. |
| 19 |
|
| 20 |
We can make this change to the profiles immediately because use.mask |
| 21 |
support has been available for a long time, and use.force is simply |
| 22 |
ignored by older versions of portage. Thoughts? |
| 23 |
|
| 24 |
Zac |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2.0.2 (GNU/Linux) |
| 27 |
|
| 28 |
iD8DBQFF1445/ejvha5XGaMRAqr1AKDy0M1EUbrQWsWD+iMRKIUhtvyteQCfUt14 |
| 29 |
qXAgR8+pR/y5mtu5EUm5U10= |
| 30 |
=geAX |
| 31 |
-----END PGP SIGNATURE----- |
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives