1 |
On Sat, 09 May 2020 15:22:52 +0200 |
2 |
Gerion Entrup <gerion.entrup@×××××.de> wrote: |
3 |
|
4 |
> I'm not sure, if Portage is capable of this, but a distinction in USE |
5 |
> flags needed to fulfil some dependency of another package and USE flags |
6 |
> actively activated by the user could be useful. |
7 |
|
8 |
Presently impossible, as how portage implements the former, is by |
9 |
churning that information via either "plz sir, set this use flag in |
10 |
your config", or via auto-tweaking config to assert "I wanted this, you |
11 |
now want it". |
12 |
|
13 |
After that happens, the information as to /who/ specified that want is |
14 |
lost. |
15 |
|
16 |
At very best you can make some inferences based on the comments |
17 |
that get injected, but that's not anywhere near 100%, esp in turn-key |
18 |
approach, or, alternatively, assert that if a flag is specified in |
19 |
configure *and* something depends on that flag being set, then its the |
20 |
dependent, not the user .... but that really isn't true on a regular |
21 |
basis. |
22 |
|
23 |
For instance, uh, USE="X" (global) -> install Foo (w/ USE="X") |
24 |
|
25 |
Foo depends on Bar[X?] |
26 |
|
27 |
So is "Bar:X" required by the user, or by "Foo", or both? |
28 |
|
29 |
And does the answer to that question depend in any way on whether B (or |
30 |
Foo) declares IUSE="+X" or IUSE="X" ? |