1 |
We have to be precise about what we are talking here: |
2 |
|
3 |
1) for NEW ebuilds added to the tree... |
4 |
> |
5 |
> So maybe it's about time that we deprecate EAPIs 0 and 1 for new |
6 |
> ebuilds. As a first step, a warning could be added to repoman that |
7 |
> would be triggered whenever a new ebuild with an EAPI less than 2 is |
8 |
> committed. |
9 |
|
10 |
it would definitely make sense to trigger a warning whenever an ancient EAPI is |
11 |
used. Remember, we're adding new features so we can use them - and we also |
12 |
want to train new recruits for using these features. |
13 |
|
14 |
So, I'm for a repoman warning for NEW ebuilds whenever EAPI<(CURRENT_EAPI-1). |
15 |
This would at the moment deprecate EAPI=0,1 (and soon also 2). |
16 |
|
17 |
2) for existing ebuilds... |
18 |
|
19 |
... it is indeed impractical to force EAPI=0 rewriting. Some of the in-between |
20 |
steps however should be deprecated. Eg. EAPI=1 and later EAPI=2... |
21 |
|
22 |
My 2ct... |
23 |
|
24 |
Cheers, Andreas |
25 |
|
26 |
|
27 |
-- |
28 |
|
29 |
Andreas K. Huettel |
30 |
dilfridge@g.o |
31 |
http://www.akhuettel.de/ |