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: Mon, 17 Jun 2013 16:49:00 -0400	[thread overview]
Message-ID: <51BF763C.60703@gentoo.org> (raw)
In-Reply-To: <51BF6D40.4040102@gmail.com>

On 6/17/2013 4:10 PM, vivo75@gmail.com wrote:
> On 06/15/13 19:02, Mike Gilbert wrote:
>> On Sat, Jun 15, 2013 at 1:01 PM, Ciaran McCreesh
>> <ciaran.mccreesh@googlemail.com> wrote:
>>> On Sat, 15 Jun 2013 12:56:00 -0400
>>> Mike Gilbert <floppym@gentoo.org> wrote:
>>>> 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.
>>> Part of the point of EAPI stability is that it doesn't just apply to
>>> current versions of package manglers.
>>>
>> So look back at the first versions which implemented EAPI 4 support,
>> and see what the behavior was implemented at the point in time.
>>
> it make sense but it stretch things a lot.
> 
> Is it possible to:
> - keep an open bug (tracker) on named eclasses/ebuilds, so we (users and
> devs) know that there is a (teoric) fallacy
> - approve it for EAPI 6
> - move all the eapi/ebuilds to EAPI 6
> - close the bugs as WONT-FIX
> 
> In any case it should be easy to port an ebuild from EAPI4 to 6, if
> gentoers want to keep things simple it could be more a version 5a than 6
> 
> regards

What on earth is a "teoric fallacy"?

I'm fine with waiting for EAPI 6 if necessary.

I would not find a tracker bug very useful, and have no intention of
starting one.


  reply	other threads:[~2013-06-17 20:49 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
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 [this message]
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=51BF763C.60703@gentoo.org \
    --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