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