From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Variancy?
Date: Sun, 5 Dec 2010 22:06:26 +0000 [thread overview]
Message-ID: <20101205220627.64452d13@snowcone> (raw)
In-Reply-To: <19708.2662.412210.696119@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On Sun, 5 Dec 2010 22:55:50 +0100
Ulrich Mueller <ulm@gentoo.org> wrote:
> I don't understand the following passage from section "The state of
> the system between functions":
That whole section was written before Portage got parallel jobs
support, and was based around what ebuilds were actually doing.
Portage's parallel jobs break those rules, and this has caused all
kinds of weirdness.
The implications are *supposed* to be that if you want to do parallel
builds, you build binary packages in parallel (being sure to only run
one lot of pkg_ functions at once), and then install those binary
packages (the usual way, so rerunning pkg_setup) serially.
Instead, Portage just installs directly, and has a whole load of
convoluted hacks to try to avoid breakage. These don't actually work,
but the bugs are hidden often enough that you can often go for quite a
long time before you end up screwing your system up... In particular,
Portage assumes that if a and b aren't in any way dependent upon each
other, then they're not going to do anything to / that's going to break
the other one, which isn't true.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-12-05 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 21:55 [gentoo-pms] Variancy? Ulrich Mueller
2010-12-05 22:06 ` Ciaran McCreesh [this message]
2010-12-05 22:13 ` Ulrich Mueller
2010-12-05 22:21 ` Ciaran McCreesh
2010-12-05 22:49 ` Ulrich Mueller
2010-12-05 22:53 ` Ciaran McCreesh
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=20101205220627.64452d13@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@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