Dnia 2014-10-30, o godz. 15:21:17 Ian Stakenvicius <[email protected]> napisał(a):
> After discussion and review by mgorny, and significantly more testing, > here's an updated version of the previous patch. > > To reiterate, this patch changes python-single-r1 so that if there is > only one supported Python implementation that can satisfy the ebuild, > then PYTHON_SINGLE_TARGET is ignored, and the ebuild is bound by the > value(s) set in PYTHON_TARGETS instead. It is not ignored but not declared, which is good. Ignoring is bad :). So I was pretty skeptic about this at first but after thinking it all over a few times, I think it will work just fine. While it benefits only the 'bad' kind of packages and adds some complexity, I believe this is a worthwhile change. Now that Python 2.6 is removed, there are many packages that support only Python 2.7. For those packages, having two control variables is pointless. We still need to keep PYTHON_TARGETS for USE dependency matches against the package but we can safely remove PYTHON_SINGLE_TARGET for it will be handled properly by (+) and (-) defaults in the eclasses. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
