From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Re: Emerge order not deterministic !?
Date: Thu, 12 Nov 2015 08:54:30 +0000 [thread overview]
Message-ID: <20151112085430.7251a76a@digimed.co.uk> (raw)
In-Reply-To: <n21jph$vjn$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On Thu, 12 Nov 2015 09:48:48 +0100, Jörg Schaible wrote:
>> > Hmmm. And how can you then ever use
> >>
> >> emerge --resume --skip-fist
> >>
> >> if not even the first build is deterministic? I skip the first
> >> package anyway only if the problematic package is the first one to
> >> build after resume, but if I cannot even rely on that?
> >
> >
> > Because it re-uses the previous build order, not re-generate a new
> > one.
>
> That's simply not true. Emerge resume calculates the order again and
> for me it starts often with a different package.
Then use emerge --keep-going and portage will take care of skipping
failing merges for you.
--
Neil Bothwick
Every morning is the dawn of a new error...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-11-12 8:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 19:35 [gentoo-user] Emerge order not deterministic !? Walter Dnes
2015-11-12 8:06 ` Alan McKinnon
2015-11-12 8:29 ` [gentoo-user] " Jörg Schaible
2015-11-12 8:30 ` Alan McKinnon
2015-11-12 8:48 ` [gentoo-user] " Jörg Schaible
2015-11-12 8:54 ` Neil Bothwick [this message]
2015-11-12 9:35 ` [gentoo-user] " Jörg Schaible
2015-11-12 9:51 ` Neil Bothwick
2015-11-15 10:52 ` [gentoo-user] " Hans
2015-11-12 9:04 ` [gentoo-user] " Alan McKinnon
2015-11-12 9:32 ` [gentoo-user] " Jörg Schaible
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=20151112085430.7251a76a@digimed.co.uk \
--to=neil@digimed.co.uk \
--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