From: "Piotr Jaroszyński" <peper@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Phase invariancy and exclusivity requirements
Date: Mon, 12 Nov 2007 14:31:17 +0100 [thread overview]
Message-ID: <200711121431.18077.peper@gentoo.org> (raw)
In-Reply-To: <47384686.8030506@gentoo.org>
On Monday 12 of November 2007 13:26:46 Marijn Schouten (hkBst) wrote:
> What exactly is the difference between this valid situation and the
> previous invalid one?
between | | are things that can be done in parallel.
invalid:
a_pkg_setup b_pkg_setup a_build b_build | a_merge | b_merge
valid:
a_pkg_setup b_pkg_setup a_build_binary b_build_binary | a_binary_pkg_setup |
a_binary_merge | b_binary_pkg_setup | b_binary_merge
Note that pkg_setup is run twice for the second case, so when the merge order
is a then b, b_pkg_setup is aware of the changes that a_merge did, which is
not the case in first situation.
--
Best Regards,
Piotr Jaroszyński
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-12 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 22:40 [gentoo-dev] Phase invariancy and exclusivity requirements Ciaran McCreesh
2007-11-11 19:56 ` Ciaran McCreesh
2007-11-12 12:26 ` Marijn Schouten (hkBst)
2007-11-12 13:31 ` Piotr Jaroszyński [this message]
2007-11-12 13:33 ` Fernando J. Pereda
2007-11-13 15:44 ` 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=200711121431.18077.peper@gentoo.org \
--to=peper@gentoo.org \
--cc=gentoo-dev@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