From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id C8112138010 for ; Sat, 13 Oct 2012 06:29:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6BD1321C01E; Sat, 13 Oct 2012 06:29:18 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 011C3E04C1 for ; Sat, 13 Oct 2012 06:28:38 +0000 (UTC) Received: from sera-17.lan (50-122.62-81.cust.bluewin.ch [81.62.122.50]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: sera) by smtp.gentoo.org (Postfix) with ESMTPSA id E70B733DA09 for ; Sat, 13 Oct 2012 06:28:37 +0000 (UTC) Date: Sat, 13 Oct 2012 08:28:20 +0200 From: Ralph Sennhauser To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [RFC] Drop EAPI=0 requirement for system packages. Message-ID: <20121013082820.75d280a1@sera-17.lan> In-Reply-To: <20121012211023.592e82a1@gentoo.org> References: <20121012125315.33500bbb@sera-17.lan> <20121012211023.592e82a1@gentoo.org> Organization: Gentoo Linux X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/kMW0Y.FLAa5vLDW8WGmDHN9"; protocol="application/pgp-signature" X-Archives-Salt: bed14435-b7b0-41b9-9c34-02854dea4566 X-Archives-Hash: d4e110b7e1ef9f197f6eff2d2e1961ee --Sig_/kMW0Y.FLAa5vLDW8WGmDHN9 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 12 Oct 2012 21:10:23 -0600 Ryan Hill wrote: > I'd argue against deprecating EAPI 0 any time soon though. Killing > EAPI 1 would be a better idea. I'm not for forced EAPI bumps anytime soon, but I expect EAPI 0 to be gone from tree in 3-5 years once the EAPI=3D0 requirement is lifted. Currently we have only 6 official EAPIs which is still manageable to remember the details of each. Though it might be confusing for new developers. Once we are at 20 EAPIs it will be an issue also for seasoned folks. Therefore deprecation is a given, how to go about it is certainly up to discussion. What do you see as an acceptable path here? --Sig_/kMW0Y.FLAa5vLDW8WGmDHN9 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQEcBAEBAgAGBQJQeQoPAAoJEIUJ+svaV163IX8H/iVcrxNdYdzx5Ly/dJGnNgJn i+5gNQGD5fMOzVz9X1r0PyT0jdkgFANFvSCogHt66BJcx28zz67uxMs/+67BROep efGiwcgRAwybpy4tB7X12ahWrFZcgBzBrDXkbB1QYiV5LEZHbfucvU2i6QKCrMcE eQ1YrdsqJjI2E9hbXlHB/r2oc929ozcXuJ0lFVgdV3maBxdaWZR3QMEQujfSpduM VLii2kaHj4toIFhPWz+jXuSV7gMPpPisg51AN2NOU91ct//Uv6+L+ZJhldPOwUTF E9L+/3HVYmfK+AIfB3rVTq7n13fQA+lrAZuKKc3VNL89FZUPNbGTgCsHOgNQuHk= =n2HF -----END PGP SIGNATURE----- --Sig_/kMW0Y.FLAa5vLDW8WGmDHN9--