public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Calling die in a subshell
Date: Sat, 15 Jun 2013 18:24:13 +0200	[thread overview]
Message-ID: <20130615182413.2e1b2f8a@TOMWIJ-GENTOO> (raw)
In-Reply-To: <20924.37728.751450.362549@a1i15.kph.uni-mainz.de>

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

On Sat, 15 Jun 2013 18:16:32 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:

> >>>>> On Sat, 15 Jun 2013, Mike Gilbert wrote:
> 
> > The devmanual warns that calling die in a subshell does not work.
> 
> > http://devmanual.gentoo.org/ebuild-writing/error-handling/index.html
> 
> > This warning has been obsolete for some time; modern versions of
> > Portage handle die in a subshell just fine.
> 
> > In fact, at least a couple of eclasses rely on this behavior. For
> > example, python-r1 uses subshells created by multiprocessing.eclass
> > to implement parallel "sub-phase" functions, any of which may call
> > die on failure.
> 
> > Are there any objections to removing this warning from the
> > devmanual?
> 
> PMS doesn't guarantee that die works correctly in a subshell:
> http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-12800011.3.3
> 
> So the devmanual agrees with the spec, and the eclasses need to be
> fixed.

What does it take to change future specifications to guarantee this?
What's holding this from becoming guaranteed? Why not fix the specs?

When we're considering changing this, just a reference isn't enough;
please state why it is "_not_ guaranteed". What is the reasoning?

Thank you in advance.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

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

  parent reply	other threads:[~2013-06-15 16:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 16:06 [gentoo-dev] Calling die in a subshell Mike Gilbert
2013-06-15 16:14 ` Diego Elio Pettenò
2013-06-15 16:16 ` Ulrich Mueller
2013-06-15 16:19   ` hasufell
2013-06-15 16:21     ` Diego Elio Pettenò
2013-06-15 16:25     ` Ulrich Mueller
2013-06-15 17:41       ` Michał Górny
2013-06-16 13:00       ` Ulrich Mueller
2013-06-15 16:22   ` Mike Gilbert
2013-06-15 16:24   ` Tom Wijsman [this message]
2013-06-15 16:41     ` hasufell
2013-06-15 16:43       ` Ciaran McCreesh
2013-06-15 16:45         ` hasufell
2013-06-15 16:50           ` Ciaran McCreesh
2013-06-15 16:42     ` Ciaran McCreesh
2013-06-15 16:56       ` Mike Gilbert
2013-06-15 16:58         ` hasufell
2013-06-15 17:01         ` Ciaran McCreesh
2013-06-15 17:02           ` Mike Gilbert
2013-06-17 20:10             ` vivo75
2013-06-17 20:49               ` Mike Gilbert
2013-06-18  7:06                 ` [gentoo-dev] " Duncan
2013-06-19  2:01                   ` vivo75

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=20130615182413.2e1b2f8a@TOMWIJ-GENTOO \
    --to=tomwij@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