On Wed, Oct 29, 2014 at 02:17:29PM -0400, Ian Stakenvicius wrote: > As python-single-r1.eclass is meant to ensure that a package is > bound to just one implementation when multiple implementations are > possible, usually because it is too difficult to make the package > multibuild, it would make sense to me that if there is actually just > one possible implementation…
I understand “It's too difficult for me to get this build system to work with multiple Python versions.” I'm skeptical that there are any packages where “there is actually just one possible implementation.” Still I agree that some users will want a way to say “if I ask for a package that only installs for one Python implementation, just install it without my needing to tweak my USE flags.” Personally, I'd prefer to stick with my existing PYTHON_SINGLE_TARGET. If a package doesn't like that, I can think harder about whether or not I actually need the package. My Docker images [1], for example, are single-Python implementations and I don't want to pull in another Python accidentally. Cheers, Trevor [1]: https://github.com/wking/dockerfile -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
