From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NYGEl-00018b-8e for garchives@archives.gentoo.org; Fri, 22 Jan 2010 09:55:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 414F8E0838; Fri, 22 Jan 2010 09:55:16 +0000 (UTC) Received: from petteriraty.eu (host.petteriraty.eu [188.40.80.83]) by pigeon.gentoo.org (Postfix) with ESMTP id 01DDBE0838 for ; Fri, 22 Jan 2010 09:55:15 +0000 (UTC) Received: from [82.130.46.229] (qob5.kyla.fi [82.130.46.229]) by petteriraty.eu (Postfix) with ESMTPSA id ED1442D497 for ; Fri, 22 Jan 2010 09:55:14 +0000 (UTC) Message-ID: <4B5975FD.1010009@gentoo.org> Date: Fri, 22 Jan 2010 11:55:09 +0200 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; fi; rv:1.8.1.23) Gecko/20090916 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] EAPI-3 times and dates References: <20100122094627.TA4624b.tv@veller.net> In-Reply-To: <20100122094627.TA4624b.tv@veller.net> X-Enigmail-Version: 1.0 OpenPGP: url=http://users.tkk.fi/~praty/public.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7E7EB43A7664133B4D4CA23D" X-Archives-Salt: 5d01465c-9446-405d-bd84-6f2d2fe13769 X-Archives-Hash: c354ac0aa676309a5a8408f754c0942e This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7E7EB43A7664133B4D4CA23D Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 01/22/2010 10:58 AM, Torsten Veller wrote: > EAPI-3 was approved by the council during their last meeting (2010-01-1= 8). >=20 > Which portage versions do support it? > (I wasn't able to find it in the docs.) >=20 I haven't heard of a release that would. > When can we stabilize EAPI-3 ebuilds? > (I guess this is again a council decision?) >=20 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?) >=20 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 --------------enig7E7EB43A7664133B4D4CA23D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktZdgIACgkQcxLzpIGCsLSSFgCePWKJdTkFblDSNRmUPbLbAa2o oeQAnjJU5a6x3slmNjxTweAA9fpGlDAu =jDvy -----END PGP SIGNATURE----- --------------enig7E7EB43A7664133B4D4CA23D--