On 2020.12.07 13:14, antlists wrote:
On 07/12/2020 14:30, Grant Edwards wrote:
I ended up uninstalling packages mentioned in those 150 lines 2-3 at
a
time and until emerge was willing to update world.
After that I guess I start trying to re-install what was removed.
I do an emerge -C --oneshot to uninstall those packages. That way,
when emerge finally starts to update world, it pulls them all back
(at least, the ones that are needed) itself without me needing to
worry about it.
I don't think the --oneshot is doing anything here. It just prevents
adding an atom to the world file when emerging. Besides, in this case,
you do want it removed (if it was there) because, as you say, it will
just get pulled in again if it really is needed by something else.
This is where I wish there was an option similar to --keep-going,
that instead of the dependency calculation aborting when it gets in a
mess, it just stops the dependency calculation and emerges what it
can. I find just emerging a random selection of the things it says it
can, it usually does eventually get there ...
I agree with this one. I often find emerge fails, telling me the
reason, and then once I've fixed that (usually adding a different
package or changing some use flags) it fails in exactly the same way
for a different package. I know it couldn't find the second set of
issues if they were really dependent on the first set getting fixed,
but they are usually just more of the same.
Jack
