public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Telling emerge to continue when something goes wrong
Date: Sun, 14 Jan 2007 18:15:25 -0600	[thread overview]
Message-ID: <200701141815.38940.bss03@volumehost.net> (raw)
In-Reply-To: <45AA82FC.4090506@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1459 bytes --]

On Sunday 14 January 2007 13:22, Iván Pérez Domínguez 
<ivanperezdominguez@gmail.com> wrote about '[gentoo-user] Telling emerge 
to continue when something goes wrong':
> After installing Gentoo in different machines several times, I wonder if
> is there any way to tell emerge to keep installing as much as possible
> even when something goes wrong.

No, there's not.  But, there is a way to emerge to restart either from the 
package where it errored out (emerge --resume), or on the next package 
(emerge --resume --skipfirst).

Since emerge is a somewhat well-behaved program, it if fails it will exit 
with a non-zero exit code.  With that knowledge in hand it's easy to have 
your shell restart things.  The following (all one line) should work in 
any POSIX-compliant shell:

emerge --some-options a-bunch/of-packages || while ! 
emerge --resume --skipfirst; do :; done

I've also attached a longer system update script that I use, for reference.

In general, it's best for a program to bail out if it discovers it can't do 
everything you asked, and not do it "half-way".  The only program that 
even provides a "keep going" option is make, and all the uses I've seen of 
that option are abuses.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #1.2: sys-update --]
[-- Type: application/x-shellscript, Size: 758 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-01-15  0:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-14 19:22 [gentoo-user] Telling emerge to continue when something goes wrong Iván Pérez Domínguez
2007-01-14 20:34 ` Alex Schuster
2007-01-14 22:22   ` Iván Pérez Domínguez
2007-01-15  0:45   ` Iain Buchanan
2007-01-15  0:15 ` Boyd Stephen Smith Jr. [this message]
2007-01-15  0:47   ` Iain Buchanan
     [not found]   ` <45AAD3F6.6010309@gmail.com>
2007-01-15  1:36     ` Boyd Stephen Smith Jr.
2007-01-15  9:04       ` Jakob
2007-01-15  9:42         ` Ivan Perez
2007-01-15 12:34       ` Bo Ørsted Andresen
2007-01-15 12:56         ` Boyd Stephen Smith Jr.
2007-01-15 13:09           ` Bo Ørsted Andresen
2007-01-16  1:53 ` Bo Ørsted Andresen

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=200701141815.38940.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --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