From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id CD567138330 for ; Wed, 24 Aug 2016 15:49:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 222D421C170; Wed, 24 Aug 2016 15:49:37 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 490E921C08D for ; Wed, 24 Aug 2016 15:49:36 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id 3C5373408F9 for ; Wed, 24 Aug 2016 15:49:35 +0000 (UTC) Subject: Re: [gentoo-dev] base-system needs developers who care To: gentoo-dev@lists.gentoo.org References: <20160824020306.0df85e4c@abudhabi.paradoxon.rec> <20160824160505.3d07b9d6@abudhabi.paradoxon.rec> From: Michael Orlitzky Message-ID: Date: Wed, 24 Aug 2016 11:49:32 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 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 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 1efa36e0-91b8-4602-89e4-57eed6ed71b5 X-Archives-Hash: d2fe9874bd9ad092cde460f96066cdb5 On 08/24/2016 11:32 AM, Mike Gilbert wrote: > On Wed, Aug 24, 2016 at 10:05 AM, Lars Wendler wrote: >> Please keep in mind to *not* use EAPI-6 for base-system packages yet, so >> we can retain a somewhat stable upgrade path even for very old systems. > > What's the time frame for lifting that restriction? > > There are some key packages that base-system does not maintain, and it > would be good to have a documented guideline for it. > > For example, I maintain the dev-lang/python ebuilds, and I will > probably be jumping to EAPI 6 whenever Python 3.6 is released. > The EAPI=6 upgrade is probably already hosed; there was recently a thread on -user where a guy tried to update after 1.5 years and some dependency required EAPI=6 and his portage couldn't do it. The simple solution appears to be to download a new copy of portage and run it right out of the source tree until your system can do EAPI=6.