1 |
On 5/16/21 11:23 AM, Neil Bothwick wrote: |
2 |
> On Sun, 16 May 2021 11:11:54 +0200, n952162 wrote: |
3 |
> |
4 |
>>> My guess is that one of the USE flags changed. Compare which USE |
5 |
>>> flags is it currently installed with and which it wants for the |
6 |
>>> reinstall. It might even be that a USE flag changed in the ebuild, |
7 |
>>> even if it won't actually change what gets installed. (--changed-use |
8 |
>>> vs --new-use) |
9 |
>>> |
10 |
>> There are no use flags defined for any of the packages I did a random |
11 |
>> check for, either on the server or the client. I am worried that it is |
12 |
>> as you say: that the ebuild has a change of USE flags, which, of course, |
13 |
>> has nothing to do with me, the user. |
14 |
> As already stated, any USE flag changes would appear in the emerge |
15 |
> output, this is most likely caused by --changed-deps. Try with |
16 |
> --changed-use but without --changed-deps to see. |
17 |
> |
18 |
> |
19 |
I have introduced that into my build script. But, if it's as you say, |
20 |
the one is a subset of the other, it should have no effect on the |
21 |
output, right? |