1 |
On 6/18/21 8:13 PM, Zac Medico wrote: |
2 |
> On 6/18/21 6:01 PM, Zac Medico wrote: |
3 |
>> If emerge --depclean fails to resolve any dependencies, then it will |
4 |
>> now suggest emerge @unsatisfied-deps as the simplest possible |
5 |
>> solution, and will also suggest to unmerge @unavailable where |
6 |
>> appropriate at the end: |
7 |
>> |
8 |
>> $ emerge --depclean |
9 |
>> |
10 |
>> Calculating dependencies... done! |
11 |
>> * Dependencies could not be completely resolved due to |
12 |
>> * the following required packages not being installed: |
13 |
>> * |
14 |
>> * virtual/cdrtools pulled in by: |
15 |
>> * app-cdr/cdrdao-1.2.4 |
16 |
>> * |
17 |
>> * Have you forgotten to resolve unsatisfied dependencies prior to |
18 |
>> * depclean? The simplest possible command for this purpose is as |
19 |
>> * follows: |
20 |
>> * |
21 |
>> * emerge @unsatisfied-deps |
22 |
> |
23 |
> It turns out that @unsatisfied-deps is often unsuitable here because it |
24 |
> pulls in a bunch of @installed packages, when you really want to use |
25 |
> @world as the source of truth. |
26 |
|
27 |
The underlying reason is the same as the reason that we've never used |
28 |
@installed updates as a substitute for @world updates. It just doesn't |
29 |
work, because @installed is polluted in comparison to @world. |
30 |
-- |
31 |
Thanks, |
32 |
Zac |