Please bump Prefix Portage to latest with EAPI8
Just for my understanding, is our portage lacking EAPI=8 support, or does the ebuild need bumping to EAPI=8?
(In reply to Fabian Groffen from comment #1) > Just for my understanding, is our portage lacking EAPI=8 support, or does > the ebuild need bumping to EAPI=8? I think our portage is missing it, we first gained support upstream in .20 and some revbumps were needed to get some patches in afterwards.
I'm asking because rsync0/1/2 seem to be happy with it. Anyways, a bump won't hurt (usually).
(In reply to Fabian Groffen from comment #3) > I'm asking because rsync0/1/2 seem to be happy with it. Anyways, a bump > won't hurt (usually). sam@keeper ~/git/gentoo/dev-util/pkgdev % ebuild pkgdev-0.1.7.ebuild clean install Appending /Users/sam/Documents/git/gentoo to PORTDIR_OVERLAY... !!! Unable to do any operations on 'dev-util/pkgdev-0.1.7', since its EAPI !!! is higher than this portage version's. Please upgrade to a portage !!! version that supports EAPI '8'.
that seems fairly conclusive :)
we have massive keywording problems on python ecosystem, but new portage is now in the tree