1 |
On Tue, Mar 6, 2018 at 1:00 AM, Dirkjan Ochtman <djc@g.o> wrote: |
2 |
> On Tue, Mar 6, 2018 at 2:52 AM, Matt Turner <mattst88@g.o> wrote: |
3 |
>> |
4 |
>> In the end we might get to delete some code from portage or an eclass? |
5 |
>> Does this seem worth it? |
6 |
> |
7 |
> |
8 |
> To add to some of the points Kent made, I think so, yes: this means freeing |
9 |
> us from the cognitive overhead of thinking about older EAPIs at all, having |
10 |
> to remember the differences between those old EAPIs and the newer ones. |
11 |
> Removing that complexity from developer's minds as well as from our tooling |
12 |
> means our tooling will be we can spend our time and energy on other things, |
13 |
> which will be a win for the distribution. |
14 |
> |
15 |
> Yes, the long tail is painful: these are probably the packages that haven't |
16 |
> been upgraded before for a reason, but actually putting the finishing |
17 |
> touches on the EAPI migration will be worth it in the end. |
18 |
|
19 |
The long tail of packages were packages that by definition didn't |
20 |
require any maintenance or add to our collective cognitive overhead. |
21 |
:) |