1 |
On Sun, 20 Sep 2009 13:55:55 +0400 |
2 |
Alexey Shvetsov <alexxy@g.o> wrote: |
3 |
|
4 |
> On Воскресенье 20 сентября 2009 11:47:30 Rémi Cardona wrote: |
5 |
> > Le 20/09/2009 02:31, Ryan Hill a écrit : |
6 |
> > > If not, when can |
7 |
> > > we drop support for old EAPIs? Your opinions please. |
8 |
> > |
9 |
> > Let's drop it now. We've waited long enough. Portage with EAPI=2 has |
10 |
> > been stable for more than a year. |
11 |
> > |
12 |
> > Rémi |
13 |
> > |
14 |
> Yes its good idea to drop EAPI<2 from tree, but we should provide a way to |
15 |
> upgrade for people that don't upgrades recently. So we can: |
16 |
> 1 create a portage snapshot |
17 |
> 2 write mini how to about upgrade |
18 |
> 3 then drop EAPI=0 and EAPI=1 from tree to simplify tree |
19 |
|
20 |
We're talking about system packages, not the whole tree. There are 19951 |
21 |
ebuilds that don't declare EAPI and 1705 with EAPI=1 or EAPI="1". Even |
22 |
with a policy that all new ebuilds need to be EAPI 2, converting the |
23 |
entire tree would be several years of work IMO, at which point we'll be |
24 |
at EAPI zillion+1. |
25 |
|
26 |
|
27 |
-- |
28 |
fonts, Character is what you are in the dark. |
29 |
gcc-porting, |
30 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |