1 |
>>>>> On Tue, 10 Jan 2017, Zac Medico wrote: |
2 |
|
3 |
> On 01/10/2017 01:56 PM, Bernard Cafarelli wrote: |
4 |
>> gnustep-base/gnustep-make has a USE flag (libobjc2) masked globally in |
5 |
>> base/package.use.mask, and unmasked on specific arches in |
6 |
>> arch/{amd64,x86}/package.use.mask |
7 |
>> |
8 |
>> To get a stabilization (#579232) bug finally moving on, I wanted to |
9 |
>> leave this flag out, adding a corresponding line in |
10 |
>> base/package.use.stable.mask |
11 |
|
12 |
So do I understand this correctly, there is: |
13 |
flag in base/package.use.mask, |
14 |
-flag in arch/{amd64,x86}/package.use.mask, and |
15 |
flag in base/package.use.stable.mask? |
16 |
|
17 |
>> But repoman replied with a batch of dependency.bad errors... |
18 |
>> Does package.use.mask (stable and ~arch) have a higher priority on |
19 |
>> package.use.stable.mask (stable only)? Bug or intended behavior? |
20 |
|
21 |
> If I understand you correctly, then it's the intended behavior. If the |
22 |
> flag is masked in both package.use.mask and package.use.stable.mask, |
23 |
> then the package.use.stable.mask setting is irrelevant because both |
24 |
> package.use.mask and package.use.stable.mask are considered when |
25 |
> calculating use.mask settings for any given package. |
26 |
|
27 |
I believe this is not correct. package.use.stable.mask should take |
28 |
precedence within the same profile: |
29 |
https://projects.gentoo.org/pms/6/pms.html#x1-58002r1 |
30 |
|
31 |
The problem here is rather that the base profile is processed as a |
32 |
whole before the arch specific profile, so you end up with -flag from |
33 |
the arch profile. |
34 |
|
35 |
Putting flag in arch/{amd64,x86}/package.use.stable.mask should solve |
36 |
it. |
37 |
|
38 |
Ulrich |