For the newest version: * This package is still using EAPI=4. This results in package * dependencies violating PMS and causing issues for package managers. * For this reason, using EAPI=4 in new Python packages will be banned * on 2015-03-20 (2 years and 6 months after approving EAPI 5). Please *finally* bump EAPI of this package. If this isn't done on time, I will bump EAPI in a revbump.
i'm not interested in moving core packages to EAPI=5 yet. i'd rather strip out python from these packages.
(In reply to SpanKY from comment #1) There is no reason to keep "core" packages on EAPI 4.
After a conversion in IRC, we reached the following compromise: We can go to EAPI 5, so long as we keep an EAPI 4 version around, possibly without the newer python eclass support. vapier wants to support system upgrades for longer than the council mandate, and this help facilitate that.
Thanks for taking care of this :). That's pretty much what I wanted anyway.
+*file-5.22-r1 (21 Mar 2015) + + 21 Mar 2015; Michał Górny <mgorny@gentoo.org> +file-5.22-r1.ebuild, + file-9999.ebuild: + EAPI bump, bug #543160.