1 |
On 2018-07-24 1:55 p.m., Dennis Schridde wrote: |
2 |
> Am Dienstag, 24. Juli 2018, 19:15:19 CEST schrieb Ian Stakenvicius: |
3 |
>> |
4 |
>> This is getting a little scary as to what is overriding what, within a |
5 |
>> repo. |
6 |
> |
7 |
> I also tried to untangle this in my email from Sat, 21 Jul 2018 14:45:12 +0000 |
8 |
> |
9 |
|
10 |
Yeah I did see that after posting my message; I believe both of our |
11 |
lists align. |
12 |
|
13 |
|
14 |
> |
15 |
>> Lets take a look at what we -can- do right now: |
16 |
>> |
17 |
>> (a) use flag can be set globally by the repo |
18 |
>> (b) ebuild IUSE can set (and unset?) a flag's state |
19 |
>> (c) make.defaults and package.use from the profile (that generally is |
20 |
>> defined within the gentoo repo) sets/unsets a flag's state |
21 |
>> (d) make.conf sets/unsets a flag's state |
22 |
>> (e) /etc/portage/package.use sets/unsets a flag's state |
23 |
>> (f) {,package.}use.{mask,force} from the profile overrides a-e |
24 |
>> (g) /etc/portage/profile/{,package.}use.{mask,force} overrides f |
25 |
>> |
26 |
>> That's a lot of possible state overriding. |
27 |
> |
28 |
> I, too, would hope that at some point later, independently of this discussion, |
29 |
> the algorithm for determining what use flags are active for a certain package |
30 |
> could be simplified. |
31 |
> |
32 |
|
33 |
I don't think the process needs to be simplified much more than this; |
34 |
each layer above has its purpose. However I do very much want to |
35 |
caution on making it more complicated, especially with the addition of |
36 |
syntax that allows setting or ignoring useflag state changes in a way |
37 |
that will jumble up these layers. |