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 1S6hU0-0006HQ-0u for garchives@archives.gentoo.org; Sun, 11 Mar 2012 12:02:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4B22BE07CE; Sun, 11 Mar 2012 12:02:25 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 661B6E0777 for ; Sun, 11 Mar 2012 12:01:51 +0000 (UTC) Received: from [192.168.1.33] (219.Red-2-137-8.dynamicIP.rima-tde.net [2.137.8.219]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id E15AE1B4004 for ; Sun, 11 Mar 2012 12:01:49 +0000 (UTC) Subject: [gentoo-dev] Deprecate EAPI1? From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-rMRWIjejLRKYBdqgFc+2" Date: Sun, 11 Mar 2012 13:01:46 +0100 Message-ID: <1331467306.11661.2.camel@belkin4> 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 X-Mailer: Evolution 2.32.3 X-Archives-Salt: 6a7d3f55-ffbd-4892-93d2-be075f970d0a X-Archives-Hash: e79c541d7f636f7888415d9ba8fd6dcd --=-rMRWIjejLRKYBdqgFc+2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable After reading previous discussion: http://help.lockergnome.com/linux/gentoo-dev-Deprecate-EAPIs--ftopict530567= .html Looks like preventing NEW commits from using eapi1 (via repoman) could be done without major issues. This could even being done also for eapi2 as it's close enough to eapi3, but I don't have a strong opinion about eapi2 deprecation (personally, I try to always use latest eapi if eclass allows me to do so). Any thoughts on this? Thanks --=-rMRWIjejLRKYBdqgFc+2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk9clCoACgkQCaWpQKGI+9Qo+ACdGWvMZDr5KKWuQHMmvFY+vksL LNQAniyPrPy9v2ynSlRDHvVxeXb45XJi =E9Nu -----END PGP SIGNATURE----- --=-rMRWIjejLRKYBdqgFc+2--