From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Patch for python.eclass
Date: Mon, 25 Oct 2010 07:17:46 +0100 [thread overview]
Message-ID: <20101025071746.3ac20ed1@snowcone> (raw)
In-Reply-To: <201010242349.33064.Arfrever@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
On Sun, 24 Oct 2010 23:47:56 +0200
Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> wrote:
> > > Usage of new EAPIs in the tree is not allowed before council
> > > approval.
> >
> > python.eclass doesn't use any EAPIs, it only provides support for
> > ebuilds, which use given EAPIs (without EAPI="4").
>
> I forgot to say that this patch doesn't introduce usage of any
> feature absent in EAPI="3" and present in current draft of EAPI="4",
> but changes API of python.eclass in EAPI="4".
For all we know, EAPI 4 may be completely changed next week and then
allowed in the tree the week after. Then people looking at your eclass
will incorrectly assume that it supports the approved EAPI 4.
EAPI 4's current state used to be "closed, and approved subject to
Portage implementation", but due to the huge delays in that there have
been a number of things since then that the Council has voted on that
no-one has provided PMS patches or even approximate wording for. Unless
you've been keeping very close track of that, you don't even know what
EAPI 4 is likely to contain, let alone what it eventually will
contain...
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-10-25 6:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 1:33 [gentoo-dev] Patch for python.eclass Arfrever Frehtes Taifersar Arahesis
2010-10-18 7:06 ` [gentoo-dev] " Mike Frysinger
2010-10-18 15:10 ` Arfrever Frehtes Taifersar Arahesis
2010-10-18 15:15 ` Diego Elio Pettenò
2010-10-22 7:56 ` Mike Frysinger
2010-10-23 19:21 ` Arfrever Frehtes Taifersar Arahesis
2010-10-18 15:26 ` [gentoo-dev] " Petteri Räty
2010-10-24 18:49 ` Arfrever Frehtes Taifersar Arahesis
2010-10-24 18:54 ` Petteri Räty
2010-10-24 19:22 ` Arfrever Frehtes Taifersar Arahesis
2010-10-24 21:47 ` Arfrever Frehtes Taifersar Arahesis
2010-10-25 6:17 ` Ciaran McCreesh [this message]
2010-10-26 19:46 ` [gentoo-dev] EAPI 4 features not yet in PMS (was: Patch for python.eclass) Ulrich Mueller
2010-10-23 20:54 ` [gentoo-dev] Patch for python.eclass Arfrever Frehtes Taifersar Arahesis
2010-10-23 20:57 ` Markos Chandras
2010-10-24 18:29 ` Petteri Räty
-- strict thread matches above, loose matches on Subject: below --
2010-09-20 1:18 Arfrever Frehtes Taifersar Arahesis
2010-09-24 17:39 ` Arfrever Frehtes Taifersar Arahesis
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=20101025071746.3ac20ed1@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--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