Re: Emerge --resume --skipfirst

If you are in the mood for a hack, add --keep-going to the
EMERGE_DEFAULT_OPTS.
Then, in a case like "i actually don't want to compile this
huge package", you can just kill the respective compilation
process; emerge registers this a a failed compilation
and keeps going with the remaining packages.

Note: This is not recommended by any dev, so try at your own risk.

On 4/27/26 18:37, Peter Humphrey wrote:
> Greetings,
> 
> I remember a dev remarking not long ago that this, the subject, had been
> superseded. Well, I had cause to use it today.
> 
> After wrestling with a maze of USE conflicts after the latest sync, I decided
> to cut the Gordian knot with an 'emerge -e @world'.
> 
> All was going smoothly until I noticed it was compiling Chromium; that's when
> I remembered installing that to test a website. It took 13 hours. So I aborted
> the emerge. What I should have done next is to 'emerge --resume --skipfirst'
> and uninstall chromium later. I hadn't the presence of mind, though, so I
> uninstalled chromium straight away and had to restart the -e @world from the
> beginning.
> 
> Ho hum.
>