| Summary: | python eclass tries to compile/install for every entry of USE_PYTHON, also the deps are not checked/met | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Sachau <tommy> |
| Component: | New packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | floppym |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Thomas Sachau
2012-04-03 15:41:12 UTC
Adding Arfrever and myself as the last to touch that. I think this is simply happening because you have USE_PYTHON="2.6 ..." but do not have python-2.6 installed. We could probably make that throw a more useful error, but that's a different bug. Adjusting title and changing assignee This should still be fixed, even if the current python eclass makes it hard to understand and fix issues without introducing new ones. USE_PYTHON is troublesome. Especially with binary packages. If packages build with USE_PYTHON="2.7 3.1 3.2", and try to install these packages into the root with USE_PYTHON="2.7 3.1" and python:2.7 python:3.1 installed, installation fails. I think there are three approach to solve this problem 1.USE_PYTHON should be treat as a kind of dependency 2.Can portage drop the python:3.2 part with warning? 3.Just install all files without check python versions. *** This bug has been marked as a duplicate of bug 402813 *** |