Created attachment 344742 [details, diff] vte-0.28.2-r205.ebuild.patch Tested with dev-util/a8, works. pyvte.pc does not seem to have any python-version specific information, so that can be ignored for now
Created attachment 344746 [details, diff] vte-0.28.2-r205.ebuild.diff don't run python_foreach_impl unconditionally, rather wrap the phases depending on python useflag, thanks to mgorny
Created attachment 344748 [details, diff] vte-0.28.2-r205.ebuild.diff I missed one.
+*vte-0.28.2-r205 (07 Apr 2013) + + 07 Apr 2013; Pacho Ramos <pacho@gentoo.org> +vte-0.28.2-r205.ebuild, + -vte-0.34.1.ebuild: + Move to python-r1 (#464996 by Julian Ospald), drop old. +
Reopening since the ebuild needs to be fixed. Multi-impl support must not be enforced at any cost, and especially not in cost of serious QA violations. And repeatedly building the whole vte and discarding n-1 builds of is one of the kind. Looking at it, I doubt there's a clear way of building for multiple impls without heavy hackery which is simply not worth the effort. I'd just go for python-single-r1 here, and python-single-r1 all the deps. To use multi-impl support, you would have to: 1) do some conditional building and ugly-symlinking Build the whole thing for one impl, then symlink .la and libs to others and 'emake -C python' there. That's just ugly, and hard to achieve. You'd have to hack autotools a fair bit. 2) build all the impls in the same dir (untested) Theoretically you could just build all the impls one by one. Then the common parts will not be rebuilt, but you'd have to hack it hard to have split python parts and more to switch the Python impls. Just don't do this.
It was done properly in a couple of ebuilds already, see gtk-vnc for example. It just needs a bit more care than usual.
+*vte-0.28.2-r206 (07 Apr 2013) + + 07 Apr 2013; Julian Ospald <hasufell@gentoo.org> -vte-0.28.2-r205.ebuild, + +vte-0.28.2-r206.ebuild: + revise python logic to avoid rebuilding non-python parts
