From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI-3 times and dates
Date: Fri, 22 Jan 2010 11:55:09 +0200 [thread overview]
Message-ID: <4B5975FD.1010009@gentoo.org> (raw)
In-Reply-To: <20100122094627.TA4624b.tv@veller.net>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On 01/22/2010 10:58 AM, Torsten Veller wrote:
> EAPI-3 was approved by the council during their last meeting (2010-01-18).
>
> Which portage versions do support it?
> (I wasn't able to find it in the docs.)
>
I haven't heard of a release that would.
> When can we stabilize EAPI-3 ebuilds?
> (I guess this is again a council decision?)
>
When a Portage version supporting EAPI-3 is stable. Council can
acknowledge at this point.
> How long do we have to provide ebuilds for older EAPIs?
> (We can drop them as long as users are able to upgrade to an EAPI-3
> capable package-manager for at least one year from now/after
> stabilisation?)
>
Normally ebuild developers can just use the latest. As you said the only
thing that matters is the package manager upgrade path and that only
concerns a few packages.
Regards,
Petteri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2010-01-22 9:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 8:58 [gentoo-dev] EAPI-3 times and dates Torsten Veller
2010-01-22 9:55 ` Petteri Räty [this message]
2010-02-23 10:49 ` [gentoo-dev] Who is interested by maintaining gnash ? Romain Perier
2010-01-29 21:43 ` [gentoo-dev] EAPI-3 times and dates Zac Medico
2010-01-29 21:45 ` Jacob Godserv
2010-01-29 21:49 ` Zac Medico
2010-01-31 14:47 ` Ciaran McCreesh
2010-01-31 17:51 ` Zac Medico
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=4B5975FD.1010009@gentoo.org \
--to=betelgeuse@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