public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Calling die in a subshell
Date: Sat, 15 Jun 2013 12:56:00 -0400	[thread overview]
Message-ID: <CAJ0EP42rN1TSXD2YJG07u3j4ZsW86X6LioZemXRKZs1G9jmfig@mail.gmail.com> (raw)
In-Reply-To: <20130615174230.33a7592c@googlemail.com>

On Sat, Jun 15, 2013 at 12:42 PM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Sat, 15 Jun 2013 18:24:13 +0200
> Tom Wijsman <TomWij@gentoo.org> wrote:
>> What does it take to change future specifications to guarantee this?
>
> You can have it from EAPI 6 onwards.
>
>> What's holding this from becoming guaranteed? Why not fix the specs?
>
> The specs accurately reflect Portage behaviour at the time the specs
> were approved. The point of a stable EAPI is that once approved it
> doesn't change.
>

From the council log, the main objection I saw was that we didn't want
to change the behavior of existing ebuilds.

In this particular case, we know that Portage has been properly
handling die in a subshell since at least EAPI 4 was approved.

I don't use Paludis, but we may have a similar situation there.

If we find that all known implementations of PMS/EAPI 4 have
implemented a certain behavior, making a change to that version of PMS
to properly document the behavior seems reasonable.


  reply	other threads:[~2013-06-15 16:56 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
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 [this message]
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=CAJ0EP42rN1TSXD2YJG07u3j4ZsW86X6LioZemXRKZs1G9jmfig@mail.gmail.com \
    --to=floppym@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