Summary: | sys-apps/systemd: (still) relies on Gentoo-specific python-config-X.Y | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 445592 |
Description
Michał Górny
2013-10-17 17:36:00 UTC
-9999 fixed. A modern note: if you're using python-r1, python-single-r1 or python-any-r1, it's not necessary to use 'python-config-X.Y' or 'pythonX.Y-config' anymore. The eclass puts a local symlink to proper 'python-config' variant in $PATH, so the build system can just take 'python-config' and it will get the version desired. If the build system in question respects PYTHON and looks for appropriate pythonX.Y-config itself, great! If it doesn't, there's no need to hack it in. Just let it use python-config and the eclass will do the rest. Oh, and the releases having it are obviously long gone ;). |