EAPI 2 removal bug: https://bugs.gentoo.org/648050

It seems like tons of churn to update old stable ebuilds to a new
EAPI, just for its own sake. Take https://bugs.gentoo.org/648154 for
example. New ebuild added with EAPI 6 bumped from EAPI 2. Otherwise
functionally identical. Now asking arch teams to retest and
restabilize. Multiply by 100 or more.

In the end we might get to delete some code from portage or an eclass?
Does this seem worth it?

Reply via email to