1 |
On Thu, Jun 11, 2015 at 12:55 PM, Alexis Ballier <aballier@g.o> wrote: |
2 |
> On Thu, 11 Jun 2015 18:33:36 +0200 |
3 |
> Ulrich Mueller <ulm@g.o> wrote: |
4 |
> |
5 |
>> >> Maintainers can still use --force if there is no other way. |
6 |
>> |
7 |
>> > i'm definitely not convinced it is good practice to encourage people |
8 |
>> > to do that ;) |
9 |
>> |
10 |
>> People are strongly encouraged to update their ebuilds to a newer |
11 |
>> EAPI. ;) There are few EAPI 1 ebuilds left and the point is to prevent |
12 |
>> adding new ones accidentally. |
13 |
>> |
14 |
>> > also, it seems eapis-banned is not just about new ebuilds but also |
15 |
>> > when there happens to be an ancient ebuild in the same directory |
16 |
>> |
17 |
>> Yes, and that repoman behaves this way is the very reason why EAPIs |
18 |
>> 1 and 2 haven't been banned already one year ago. After all, this was |
19 |
>> a council decision: |
20 |
>> https://projects.gentoo.org/council/meeting-logs/20140225.txt |
21 |
> |
22 |
> |
23 |
> i agree, but what worries me is that you suddenly introduced repoman |
24 |
> errors for a bunch of packages for which there is no clear ETA on when |
25 |
> these can be fixed (i think qa policy is to not bump eapi in place) |
26 |
> |
27 |
> this is not just about "fixing" a line in an ebuild, it is about proper |
28 |
> testing for stabilization and e.g. ocaml is definitely not a package |
29 |
> whose stabilization should be done lightly |
30 |
> |
31 |
|
32 |
These errors are not user-visible. I really don't have a problem with |
33 |
repoman errors for deprecated features. |
34 |
|
35 |
We've been discouraging EAPI 1 for a while now. This just raises the |
36 |
volume a bit, while still not creating any hard problems during the |
37 |
transition. |
38 |
|
39 |
Sure, it would be nice if repoman only complained for new ebuilds, |
40 |
since that is the policy, but honestly making noise about old ones is |
41 |
probably useful, just so that we can keep their removal on the radar. |
42 |
|
43 |
Also, EAPI 1 and 2 WERE banned by the Council. Whether or not |
44 |
repoman's settings were adjusted has nothing to do with the fact that |
45 |
they were banned for new ebuilds. |
46 |
|
47 |
-- |
48 |
Rich |