On Tue, Mar 6, 2018 at 2:52 AM, Matt Turner wrote: > In the end we might get to delete some code from portage or an eclass? > Does this seem worth it? > To add to some of the points Kent made, I think so, yes: this means freeing us from the cognitive overhead of thinking about older EAPIs at all, having to remember the differences between those old EAPIs and the newer ones. Removing that complexity from developer's minds as well as from our tooling means our tooling will be we can spend our time and energy on other things, which will be a win for the distribution. Yes, the long tail is painful: these are probably the packages that haven't been upgraded before for a reason, but actually putting the finishing touches on the EAPI migration will be worth it in the end. It might have been even better if Andreas or someone else had announced this project/discussed the trade-offs before starting it. Cheers, Dirkjan