1 |
On 08/24/2016 11:32 AM, Mike Gilbert wrote: |
2 |
> On Wed, Aug 24, 2016 at 10:05 AM, Lars Wendler <polynomial-c@g.o> wrote: |
3 |
>> Please keep in mind to *not* use EAPI-6 for base-system packages yet, so |
4 |
>> we can retain a somewhat stable upgrade path even for very old systems. |
5 |
> |
6 |
> What's the time frame for lifting that restriction? |
7 |
> |
8 |
> There are some key packages that base-system does not maintain, and it |
9 |
> would be good to have a documented guideline for it. |
10 |
> |
11 |
> For example, I maintain the dev-lang/python ebuilds, and I will |
12 |
> probably be jumping to EAPI 6 whenever Python 3.6 is released. |
13 |
> |
14 |
|
15 |
The EAPI=6 upgrade is probably already hosed; there was recently a |
16 |
thread on -user where a guy tried to update after 1.5 years and some |
17 |
dependency required EAPI=6 and his portage couldn't do it. |
18 |
|
19 |
The simple solution appears to be to download a new copy of portage and |
20 |
run it right out of the source tree until your system can do EAPI=6. |