From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Telling emerge to continue when something goes wrong
Date: Mon, 15 Jan 2007 10:17:00 +0930 [thread overview]
Message-ID: <1168822020.10384.20.camel@orpheus> (raw)
In-Reply-To: <200701141815.38940.bss03@volumehost.net>
On Sun, 2007-01-14 at 18:15 -0600, Boyd Stephen Smith Jr. wrote:
> 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).
I should add that --skipfirst is sometimes "bad" because it ignores
dependencies. If you let emerge do it, then you could only resume
packages whose dependencies were satisfied.
cya,
--
Iain Buchanan <iaindb at netspace dot net dot au>
When a fellow says, "It ain't the money but the principle of the thing,"
it's the money.
-- Kim Hubbard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-15 0:58 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.
2007-01-15 0:47 ` Iain Buchanan [this message]
[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=1168822020.10384.20.camel@orpheus \
--to=iaindb@netspace.net.au \
--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