Re: Emerge --resume --skipfirst

On 4/28/26 9:12 AM, Peter Humphrey wrote:
> On Tuesday, 28 April 2026 13:10:31 British Summer Time Philipp Ludwig wrote:
>> The idea was that with --keep-going you would not abort an emerge
>> (as outlined in your original mail) but just abort the specific package
>> compilation process (in this case, google-chrome).
>> emerge would then just skip this particular package.
> Yes, I see that. My question was: once the -e @world had been interrupted,
> what command should I give it to resume. I know about --resume --skipfirst,
> which is how I started this thread.
>


Just do a emerge --resume and that's it.  It will apply the --skipfirst 
from make.conf.

Now that I think about this, I think it is --keep-going that I have in 
make.conf.  Be right back.  Yep.  I got the two confused for some 
reason.  I don't have --skipfirst in make.conf but do have 
--keep-going.  So, if you stop emerge and want to skip Chrome, just 
emerge --resume --skipfirst and it should skip Chrome.  Just make sure 
that only Chrome is actively compiling.  Sometimes two packages will be 
working at the same time.  If you have two or more compiling at the same 
time, I'm not sure how emerge will handle that.  I don't think I've ever 
ran into that before.  :/

It seems emerge has so many options, it's hard to keep them all 
straight.  ;-)

Dale

:-)  :-)