public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New profile 17: How urgent is the rebuild of world technically?
Date: Sun, 3 Dec 2017 15:16:26 +0100	[thread overview]
Message-ID: <20171203141626.w2tg7wxop2eyfukg@solfire> (raw)
In-Reply-To: <20171203140936.GA2375@inspiron.homenetwork>

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



  reply	other threads:[~2017-12-03 14:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03  2:15 [gentoo-user] New profile 17: How urgent is the rebuild of world technically? tuxic
2017-12-03  2:30 ` Michael Orlitzky
2017-12-03  2:32   ` Adam Carter
2017-12-03  2:44     ` Michael Orlitzky
2017-12-03  3:26   ` tuxic
2017-12-03  3:35     ` Heiko Baums
2017-12-03  3:45       ` tuxic
2017-12-03  4:15         ` Heiko Baums
2017-12-03  9:53           ` Peter Humphrey
2017-12-03 11:56             ` Heiko Baums
2017-12-03 12:55               ` Dale
2017-12-03 14:09                 ` Spackman, Chris
2017-12-03 14:16                   ` tuxic [this message]
2017-12-03 14:39                     ` Heiko Baums
2017-12-03 15:25                       ` Peter Humphrey
2017-12-03 15:57                       ` Neil Bothwick
2017-12-03 14:36                   ` Heiko Baums
2017-12-03 14:27                 ` Heiko Baums
2017-12-04  1:08                   ` Dale
2017-12-04  1:18                     ` Heiko Baums
2017-12-04  1:48                       ` Walter Dnes
2017-12-03  5:26         ` Adam Carter
2017-12-03 10:51         ` Neil Bothwick
2017-12-03  3:47     ` Heiko Baums
2017-12-06 23:59     ` Frank Steinmetzger
2017-12-07  8:08       ` Neil Bothwick
2017-12-04 17:48   ` Stefan G. Weichinger
2017-12-04 20:21     ` Michael Orlitzky
2017-12-05  9:16       ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171203141626.w2tg7wxop2eyfukg@solfire \
    --to=tuxic@posteo.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox