On 12/03 09:09, Spackman, Chris wrote: > On 2017/12/03 at 06:55am, Dale wrote: > > > I think I get what you are saying. If for example you start a > > emerge -e world, a emerge -uDN world or something and then stop it > > before it finishes, running emerge --resume should pick up where you > > left off. > > Another helpful option, which I don't think has been mentioned yet, is > --skipfirst. With --resume, this is helpful when a relatively > unimportant package fails to compile. Emerge will skip the one that > failed (because it would be the first one in the resumed emerge) and > continue on. Later, I go back and see about getting the failed package > to work. I don't think that --skipfirst is a good idea if an important > package (one that will affect many other packages) fails. But, I am > not an expert on that stuff. > > So, if: > > emerge -e @world > > fails (on a relatively unimportant package), you could use: > > emerge --resume --skipfirst > > to continue. I am actually almost 75% done with the system rebuild and > have had to do this so far with cdrdao and spideroak-bin (which > probably doesn't matter as it is a -bin package). > > -- > Chris Spackman > > GNU Terry Pratchett > >
Hi, what is about emerge -e @world --keep-going instead? Cheers Meino
