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-50192-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1S6svW-0001xC-CL
	for garchives@archives.gentoo.org; Mon, 12 Mar 2012 00:15:50 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 7DD14E09BA;
	Mon, 12 Mar 2012 00:15:41 +0000 (UTC)
Received: from mail-iy0-f181.google.com (mail-iy0-f181.google.com [209.85.210.181])
	by pigeon.gentoo.org (Postfix) with ESMTP id 13D38E098A
	for <gentoo-dev@lists.gentoo.org>; Mon, 12 Mar 2012 00:15:02 +0000 (UTC)
Received: by iaoo28 with SMTP id o28so7169702iao.40
        for <gentoo-dev@lists.gentoo.org>; Sun, 11 Mar 2012 17:15:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=3faRrMm+ZE9S88oXQOXWFCb2SYlK4DTBb4fRR3+5p1E=;
        b=luN+rDcsPl7Hh0F2N/NiG26Orf0Ct18enPaA9N5Cd0vjnvp4W0bSX9uJVjMeNrsAdm
         qvcDNosrLmYpl112MV49Yq4RAa4pqaETYY4Fh2wCjIDIP4Tlg/XT2bKXEtZ1bNTaEoma
         o4JaA+rSRy/357/tJ/xXa0cJhwOFYKB23LpcEqSvdv9YIPZGkytf3BrN0qqm9jh4suQ/
         VmKCZb3bVfYf0vqCzAn9jK6DiVk1pi3NrvBr2XcDrlrILmuQ3Ycp1JIfgikvpeRASgz4
         /PEjqKD128/7esblXw3nOpXtLPXQVDklArr08ZDZgEd1xXW+H7NJVDLyhvE2nLRwbIeJ
         En0A==
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.182.15.70 with SMTP id v6mr5988183obc.13.1331511302486; Sun,
 11 Mar 2012 17:15:02 -0700 (PDT)
Received: by 10.60.33.234 with HTTP; Sun, 11 Mar 2012 17:15:02 -0700 (PDT)
In-Reply-To: <CABDyM6Ttfabr6KBqsn+9rSPm6ENRPN2nxp4ptWm2sc1jcUWmLQ@mail.gmail.com>
References: <41490c1dd7ca44bcbda73b2032982596@HUBCAS1.cs.stonybrook.edu>
	<CABDyM6Ttfabr6KBqsn+9rSPm6ENRPN2nxp4ptWm2sc1jcUWmLQ@mail.gmail.com>
Date: Mon, 12 Mar 2012 00:15:02 +0000
Message-ID: <CAD6zcDzwBr2bDp2Nf1CLgpSA30um=SbKoacsrF3raLPcFLTmEA@mail.gmail.com>
Subject: Re: [gentoo-dev] Deprecate EAPI1?
From: Francesco Riosa <vivo75@gmail.com>
To: gentoo-dev@lists.gentoo.org
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt: ca8d1161-b87b-453e-81ca-68895aab4770
X-Archives-Hash: cdf8f0ded69b5f1317a624d2abb54818

top-posting me too to avoid more confusion, sorry

Se my other reply to this thread, upgrading in place an old gentoo
install is nearly impossible, it's so bad that glibc breakage can
occour, that require a knowledge of the system so high that everything
else become nuances of a vague problem.
Tell everyone that it's not possible to upgrade a 2009 system id more
honest and free everybody from forever compatibility slavery.

To be able to upgrade a gentoo installation as old as five years is
interesting and valuable but require an effort that has yet to be
made.

P.S. I'm neutral about EAPI 1 deprecation, just stating that forever
support is a chimera right now

2012/3/11 Richard Yao <ryao@cs.stonybrook.edu>:
> 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
>