1 |
El mar, 16-10-2012 a las 23:42 -0600, Ryan Hill escribió: |
2 |
> On Sat, 13 Oct 2012 08:28:20 +0200 |
3 |
> Ralph Sennhauser <sera@g.o> wrote: |
4 |
> |
5 |
> > On Fri, 12 Oct 2012 21:10:23 -0600 |
6 |
> > Ryan Hill <dirtyepic@g.o> wrote: |
7 |
> > |
8 |
> > > I'd argue against deprecating EAPI 0 any time soon though. Killing |
9 |
> > > EAPI 1 would be a better idea. |
10 |
> > |
11 |
> > I'm not for forced EAPI bumps anytime soon, but I expect EAPI 0 to be |
12 |
> > gone from tree in 3-5 years once the EAPI=0 requirement is lifted. |
13 |
> |
14 |
> How many packages in the tree don't define EAPI at all? It's been a while |
15 |
> since I looked, but I remember it was a pretty big number. Maybe things have |
16 |
> changed. |
17 |
> |
18 |
> > Currently we have only 6 official EAPIs which is still manageable to |
19 |
> > remember the details of each. Though it might be confusing for new |
20 |
> > developers. Once we are at 20 EAPIs it will be an issue also for |
21 |
> > seasoned folks. |
22 |
> |
23 |
> Agreed. We will definitely have to do some pruning at some point. |
24 |
|
25 |
Would be easier to prune old versions if we "force" them to be less |
26 |
using at least preventing new ebuilds to use them. For example, what is |
27 |
the advantage for a new ebuild to still rely on old src_compile phase |
28 |
instead of src_prepare/configure...? |
29 |
|
30 |
> |
31 |
> > Therefore deprecation is a given, how to go about it is certainly up to |
32 |
> > discussion. What do you see as an acceptable path here? |
33 |
> |
34 |
> I think an EAPI becomes a candidate for removal when the number of packages |
35 |
> using it becomes small enough that a sufficiently motivated/bored/gullible |
36 |
> person could take on the task of porting them all to a newer EAPI. EAPI 0 is |
37 |
> our baseline (all EAPIs are defined as "EAPI 0 plus/minus foo") and thus |
38 |
> should never* be removed. Anything else is fair game. |
39 |
> |
40 |
> |
41 |
> *for varying lengths of never. If it becomes completely irrelevant then |
42 |
> yeah just boot it. |
43 |
> |