1 |
On Sat, 21 Mar 2009 18:37:12 +0100 |
2 |
Patrick Lauer <patrick@g.o> wrote: |
3 |
|
4 |
> To make our lives easier I would suggest deprecating EAPI0 and |
5 |
> migrating existing ebuilds over some time to EAPI1 or higher until |
6 |
> EAPI0 can be obsoleted at some point in the future. |
7 |
> I would set the start of deprecation warnings about 3 months from now |
8 |
> and the obsoletion quite a time later, maybe 12 months from now, when |
9 |
> a sufficient amount of ebuilds has been migrated. |
10 |
|
11 |
As always, wording is important. I think having too many EAPIs in |
12 |
active use unnecessarily complicates things, such as remembering which |
13 |
features are offered by which EAPIs, etc. I think we should start |
14 |
deprecating EAPI=0 usage *now* with a repoman warning whenever a new |
15 |
ebuild is committed that does not use EAPI=1 or EAPI=2. This warning |
16 |
should encourage use of the newest EAPI, EAPI=2. Obsoleting EAPI=0 |
17 |
should occur when the decision to do so merely codifies the state of |
18 |
the tree (at 90% EAPI>0, to pick a number ), at which point the |
19 |
warning would be changed to an error. We could then use a couple of |
20 |
bugdays to convert the remainder of the ebuilds or hand them over to |
21 |
treecleaners if it's just unmaintained cruft. |
22 |
|
23 |
In a year or so, we could change the repoman warning to trigger with |
24 |
EAPI=1 also and make it point to EAPI=3 as the EAPI-of-choice. |
25 |
|
26 |
> Deprecating EAPI1 at the same time would reduce the amount of EAPIs |
27 |
> we have to think about, but since it has some changes like adding |
28 |
> src_prepare migration would not be as trivial. So I'd prefer keeping |
29 |
> it around a bit longer. |
30 |
> |
31 |
> Comments? |
32 |
|
33 |
We need to make this a part of the EAPI-upgrade process that |
34 |
whenever a new EAPI is added, we consider including another EAPI in the |
35 |
repoman warning. My hope is that at some point in the future (4 years?), |
36 |
we'll be able to cut out some of the ugly phase hacks we have in many |
37 |
eclasses that had EAPI=2 grafted onto them. |
38 |
|
39 |
/loki_val |