1 |
On Friday, 20 July 2018 08:25:05 CEST Michael Orlitzky wrote: |
2 |
> On 07/20/2018 02:12 AM, Mart Raudsepp wrote: |
3 |
> > Ok, I can see that point of view for make.conf. |
4 |
> > I can't agree with changes in other profiles though, as other profile |
5 |
> > will fall under the same category in USE_ORDER (in fact, it's the same |
6 |
> > thing, as the end USE from "defaults" comes from your selected profile |
7 |
> > and it's "parent" cascade, not taken from linux profile). But maybe you |
8 |
> > have it tested and know it's a problem. Have you? |
9 |
> |
10 |
> Yes, when you set USE=foo in profile A and USE="-foo" in profile A/B, |
11 |
> the end result is USE="foo -foo" which is the same thing as USE="-foo". |
12 |
> The default portage USE_ORDER makes the profile flags more important |
13 |
> than IUSE defaults, so the USE="-foo" from the profile clobbers any |
14 |
> IUSE="+foo" defaults. |
15 |
> |
16 |
> If no default was set in profile A, then no override would be necessary |
17 |
> in profile A/B, and the resulting USE="" would not override the IUSE |
18 |
> default. |
19 |
|
20 |
It appears to me that the difficulty stems from use flags being tri-state |
21 |
(enabled, disabled, unset), but us having only operators to enable (+) and |
22 |
disable (-) them in make.conf and profiles. |
23 |
|
24 |
What about adding a third operator, e.g. `^`, that resets a use flag to the |
25 |
unset state? |