1 |
The GLEP specify that: |
2 |
|
3 |
--snip-- |
4 |
Additional Issues |
5 |
----------------- |
6 |
|
7 |
Groups should *not* generally contain negative USE flags, as this would |
8 |
lead to confusion. Groups are intended to specify what will be enabled for |
9 |
a given role, not what will be turned off. For example, if the @KDE group |
10 |
disabled Gnome-related USE flags, and a user used ``USE="@GNOME @KDE"`` to |
11 |
specify that they wanted both Gnome *and* KDE to be used where applicable, |
12 |
chaos would ensue. However, for the sake of consistency, -flags should be |
13 |
supported even if their use is strongly discouraged. |
14 |
|
15 |
It is proposed that ``-@GROUP`` syntax should *not* be supported. Instead, |
16 |
users wishing to turn most things off could use the ``-*`` USE syntax |
17 |
along with a group (for example, @RECOMMENDED or @MINIMAL) which turned on |
18 |
flags (for example, pam and readline) which should usually be used. |
19 |
--/snip-- |
20 |
|
21 |
my two cents are to *allow* negative USE flags and parse them |
22 |
*before* the additive ones. |
23 |
|
24 |
This way we parse the USE variable twice. |
25 |
- one to chose the negative flags and expanding negative group. |
26 |
- then we parse it again adding all positives (that nullify negative ones) |
27 |
|
28 |
example |
29 |
|
30 |
:: |
31 |
|
32 |
GROUP1 flag1 flag2 |
33 |
GROUP2 flag2 flag3 |
34 |
GROUP3 @GROUP1 -@GROUP2 flag2 flag3 flag4 |
35 |
|
36 |
it's the same as: |
37 |
|
38 |
GROUP1 flag1 flag2 |
39 |
GROUP2 flag2 flag3 |
40 |
GROUP3 @GROUP1 flag3 flag4 |
41 |
|
42 |
and GROUP3 may be expanded both in: |
43 |
|
44 |
GROUP3 flag1 flag2 flag3 flag4 |
45 |
or |
46 |
GROUP3 flag1 flag2 flag2 flag3 flag4 |
47 |
|
48 |
|
49 |
-- |
50 |
gentoo-dev@g.o mailing list |