public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] has_version etc parallelisability
Date: Mon, 31 Dec 2007 14:28:44 +0000	[thread overview]
Message-ID: <20071231142844.5e2a09aa@snowcone> (raw)
In-Reply-To: <b41005390712302011ibfb1534pa5c2f18100f9693@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

On Sun, 30 Dec 2007 20:11:16 -0800
"Alec Warner" <antarus@gentoo.org> wrote:
> On 12/30/07, Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk> wrote:
> > Is it legal for ebuilds to call has_version and friends in
> > parallel? Is it legal for ebuilds to call has_version and friends
> > after the ebuild process has terminated? Discuss.
> 
> If the pm implements read/write locking on the underlying datastore
> (which it should probably have regardless of this request) then I
> don't see a problem in parallel has_version calls.

Actually, it's the communication channel that's the issue... If, for
example, has_version is implemented in terms of a request on a pipe
rather than execing a new package manager, we get into messy bash
locking territory...

> I don't get your second example..do you mean the ebuild is running
> has_version in the background and then terminating?

Yeah. Again, consider the pipe example. If the package manager closes
off the pipe when it thinks the ebuild's done, calling has_version will
get the backgrounded process SIGPIPEd.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2007-12-31 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 22:35 [gentoo-dev] has_version etc parallelisability Ciaran McCreesh
2007-12-31  3:03 ` Petteri Räty
2007-12-31 14:25   ` Ciaran McCreesh
2007-12-31  4:11 ` Alec Warner
2007-12-31 14:28   ` Ciaran McCreesh [this message]
2008-01-05  2:50     ` Brian Harring
2008-01-05  4:52       ` Ciaran McCreesh
2008-01-05 17:29         ` Luca Barbato
2008-01-05 18:55           ` Petteri Räty
2008-01-06  0:31           ` 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=20071231142844.5e2a09aa@snowcone \
    --to=ciaran.mccreesh@blueyonder.co.uk \
    --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