1 |
On 2015-10-20 at 22:11:24 -0700, zmedico@g.o wrote: |
2 |
> Any packages that are not reachable from @world are ripe for removal by |
3 |
> --depclean, so we allow their dependencies to break in order to satisfy |
4 |
> other dependencies (like in bug 563482). If you don't use --deep, then |
5 |
> emerge may try to build something that depends on one of these |
6 |
> unreachable packages with broken dependencies, such that whatever you |
7 |
> are trying to build has broken indirect dependencies (which is likely to |
8 |
> trigger a build failure like in bug 563482). |
9 |
|
10 |
I think I understand. So, one could get the hypothetical scenario: |
11 |
|
12 |
# emerge --oneshot A # which depends on B |
13 |
# emerge --update @world # shuffles stuff around breaking B |
14 |
# emerge C # which depends on A |
15 |
|
16 |
Package C's dependency is filled, so emerge goes ahead and builds C. |
17 |
Now, either C fails to build, or it is installed but fails at runtime, |
18 |
because it depends on a package which depends on a package which is |
19 |
broken. |
20 |
|
21 |
Sound about right? |
22 |
|
23 |
-- |
24 |
There are problems in today's world that cannot be |
25 |
solved by the level of thinking that created them. |
26 |
-- Albert Einstein |