1 |
On Fri, 19 Oct 2012 20:09:15 +0200 |
2 |
Pacho Ramos <pacho@g.o> wrote: |
3 |
|
4 |
> El vie, 19-10-2012 a las 14:51 -0300, Alexis Ballier escribió: |
5 |
> > On Fri, 19 Oct 2012 19:21:52 +0200 |
6 |
> > Pacho Ramos <pacho@g.o> wrote: |
7 |
> > |
8 |
> > [...] |
9 |
> > |
10 |
> > > What I am trying to say is that, if we agree latest eapi is |
11 |
> > > technically better, we need to try to get it used when possible (I |
12 |
> > > mean, when, for example, eclasses are ported) for a "QA" |
13 |
> > > reasoning. |
14 |
> > |
15 |
> > i think we all agree that there are improvements in newer eapis. |
16 |
> > |
17 |
> > what about filling bugs, preferably with patches, when such |
18 |
> > improvements are really needed ? like what was done for nuking |
19 |
> > built_with_use. |
20 |
> > |
21 |
> > arguing to death if 'should use latest eapi' should become 'must use |
22 |
> > latest eapi' will never get things done :) |
23 |
> > |
24 |
> > |
25 |
> |
26 |
> Because it will add even more work, I mean: |
27 |
> - I catch a package using and old eapi and, then, still not passing |
28 |
> --disable-silent-rules option. => First problem, I need to notice that |
29 |
> package, there are packages I simply won't notice because I don't |
30 |
> merge them ever or, simply, I don't notice that option is not being |
31 |
> used. |
32 |
|
33 |
i dont see that many blockers of bug #429308 ; it probably doesn't even |
34 |
reach 1% of packages using old eapis. perhaps because silent rules are |
35 |
not enabled by default afaik. |
36 |
|
37 |
> - I need to report a bug per each package using old eapi => I would |
38 |
> need to report a ton of bugs for bumping eapi that, probably, I could |
39 |
> have directly bumped myself if I would be allowed to (I already do it |
40 |
> in my maintained packages and maintainer-needed ones, but not for |
41 |
> others as maybe their maintainers dislike...) |
42 |
> |
43 |
> - Maintainer need to check that bug and commit the change or reject |
44 |
> the bump (in that case we would be blocked if maintainer doesn't bump |
45 |
> it for some strange reason). There are also some devs really slow to |
46 |
> reply. |
47 |
|
48 |
filling a bug has one advantage you forgot: training fellow |
49 |
developers. if you say simply bumping the eapi will get improvements for |
50 |
free (whatever they are) to the maintainer, then she will be very happy |
51 |
to bump it i'd guess and have learnt that its good practices to do so. |
52 |
|
53 |
if you volunteer to do some conversions you can probably ask people to |
54 |
grant you permission to convert their ebuilds. |
55 |
|
56 |
[...] |