On 08/24/2016 11:32 AM, Mike Gilbert wrote:
> On Wed, Aug 24, 2016 at 10:05 AM, Lars Wendler <polynomia...@gentoo.org> 
> 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.


Reply via email to