| 1 |
On 10/20/2015 05:37 PM, Rob Wortman wrote: |
| 2 |
> On 2015-10-20 at 21:44:58 +0200, bernalex@g.o wrote: |
| 3 |
>> (since it's describing somewhat complicated functionality) |
| 4 |
> |
| 5 |
> So, I'm curious what's actually going on there. If I emerge packages |
| 6 |
> with --oneshot, does that create the possibility of broken dependencies |
| 7 |
> for world-reachable packages, or does updating @world create the |
| 8 |
> possiblity of broken dependencies for oneshot'ed packages? |
| 9 |
> |
| 10 |
|
| 11 |
Any packages that are not reachable from @world are ripe for removal by |
| 12 |
--depclean, so we allow their dependencies to break in order to satisfy |
| 13 |
other dependencies (like in bug 563482). If you don't use --deep, then |
| 14 |
emerge may try to build something that depends on one of these |
| 15 |
unreachable packages with broken dependencies, such that whatever you |
| 16 |
are trying to build has broken indirect dependencies (which is likely to |
| 17 |
trigger a build failure like in bug 563482). |
| 18 |
-- |
| 19 |
Thanks, |
| 20 |
Zac |
Archives