| 1 |
On Sun, 2022-02-20 at 19:51 +0000, Neil Bothwick wrote: |
| 2 |
> |
| 3 |
> Shouldn't --keep-going have kicked in there and restarted the update? |
| 4 |
> |
| 5 |
|
| 6 |
You'd think, but --keep-going tries to recompute dependencies and if |
| 7 |
the original emerge crashes in an inconsistent state, that often seems |
| 8 |
to push the calculation over the edge, preventing portage from figuring |
| 9 |
out how to proceed. |
| 10 |
|
| 11 |
In my half-baked imagination, |
| 12 |
|
| 13 |
emerge --i-dont-care -uDN @world |
| 14 |
|
| 15 |
would build the package list normally, but then would go through them |
| 16 |
one at a time as if "emerge -1 --nodeps" was used for each. So once we |
| 17 |
know that the package list *can* be emerged in that order -- just do |
| 18 |
it, and don't try to think again. |
Archives