1 |
On 5/16/21 12:49 PM, n952162 wrote: |
2 |
> On 5/16/21 11:28 AM, Neil Bothwick wrote: |
3 |
>> On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: |
4 |
>> |
5 |
>>>>> There are no use flags defined for any of the packages I did a random |
6 |
>>>>> check for, either on the server or the client. I am worried that it |
7 |
>>>>> is as you say: that the ebuild has a change of USE flags, which, of |
8 |
>>>>> course, has nothing to do with me, the user. |
9 |
>>>> As already stated, any USE flag changes would appear in the emerge |
10 |
>>>> output, this is most likely caused by --changed-deps. Try with |
11 |
>>>> --changed-use but without --changed-deps to see. |
12 |
>>>> |
13 |
>>>> |
14 |
>>> I have introduced that into my build script. But, if it's as you say, |
15 |
>>> the one is a subset of the other, it should have no effect on the |
16 |
>>> output, right? |
17 |
>>> |
18 |
>> --changed-use is a subset of --newuse. --changed-deps is separate. |
19 |
>> |
20 |
>> |
21 |
> Ah, I oversaw that. |
22 |
> |
23 |
> Ah. why would I want to have --changed-deps anyway? That suddenly seems |
24 |
> silly. |
25 |
> |
26 |
> It's unfortunate, if there's no explanatory display if a package got |
27 |
> disqualified for that reason. |
28 |
> |
29 |
> |
30 |
|
31 |
Okay, the point is, there's some package on my system that doesn't match |
32 |
what the new version of the depending package requires? Or, just that |
33 |
there's a dependency change at all? |
34 |
|
35 |
If the former, but there's a old version of the needed packet, will |
36 |
portage link with the old version? |