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 <gentoo-dev+bounces-50191-garchives=archives.gentoo.org@lists.gentoo.org>) id 1S6sbP-0007zc-9J for garchives@archives.gentoo.org; Sun, 11 Mar 2012 23:55:03 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6247BE0920; Sun, 11 Mar 2012 23:54:54 +0000 (UTC) Received: from edge1.cs.stonybrook.edu (edge1.cs.stonybrook.edu [130.245.9.210]) by pigeon.gentoo.org (Postfix) with ESMTP id 233F4E086E for <gentoo-dev@lists.gentoo.org>; Sun, 11 Mar 2012 23:54:27 +0000 (UTC) Received: from HUBCAS2.cs.stonybrook.edu (130.245.9.207) by edge1.cs.stonybrook.edu (130.245.9.210) with Microsoft SMTP Server (TLS) id 14.1.355.2; Sun, 11 Mar 2012 19:54:21 -0400 Received: from mail-iy0-f181.google.com (209.85.210.181) by hubcas2.cs.stonybrook.edu (130.245.9.212) with Microsoft SMTP Server (TLS) id 14.1.339.1; Sun, 11 Mar 2012 19:54:25 -0400 Received: by iaoo28 with SMTP id o28so7143483iao.40 for <gentoo-dev@lists.gentoo.org>; Sun, 11 Mar 2012 16:54:24 -0700 (PDT) Precedence: bulk List-Post: <mailto:gentoo-dev@lists.gentoo.org> List-Help: <mailto:gentoo-dev+help@lists.gentoo.org> List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org> List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.50.187.231 with SMTP id fv7mr2742798igc.51.1331510064508; Sun, 11 Mar 2012 16:54:24 -0700 (PDT) Received: by 10.231.200.136 with HTTP; Sun, 11 Mar 2012 16:54:24 -0700 (PDT) In-Reply-To: <41490c1dd7ca44bcbda73b2032982596@HUBCAS1.cs.stonybrook.edu> References: <41490c1dd7ca44bcbda73b2032982596@HUBCAS1.cs.stonybrook.edu> Date: Sun, 11 Mar 2012 19:54:24 -0400 Message-ID: <CABDyM6Ttfabr6KBqsn+9rSPm6ENRPN2nxp4ptWm2sc1jcUWmLQ@mail.gmail.com> Subject: Re: [gentoo-dev] Deprecate EAPI1? From: Richard Yao <ryao@cs.stonybrook.edu> To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org> Content-Type: text/plain; charset="ISO-8859-1" X-Originating-IP: [209.85.210.181] X-Archives-Salt: 1e0b6d5b-474b-4b29-9ba6-bd3dca352634 X-Archives-Hash: 7440b8a4996b0bf6783d25c919936ee2 These must be maintained indefinitely to provide an upgrade path for older Gentoo Linux installations. It is rare, but people do upgrade old installs from time to time. Without some EAPI=1 packages, there is no path for people to use to upgrade. On Sun, Mar 11, 2012 at 8:01 AM, Pacho Ramos <pacho@gentoo.org> wrote: > 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