Summary: | app-admin/python-updater-0.8 rebuilds packages inheriting gnome-python-common.eclass | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Pipping <sping> |
Component: | New packages | Assignee: | Python Gentoo Team <python> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | gnome, rose |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output of "python-updater -p -v -v -v" |
Description
Sebastian Pipping
2010-11-09 19:07:30 UTC
Please attach output of: python-updater -p -v -v -v Created attachment 254381 [details] Output of "python-updater -p -v -v -v" (In reply to comment #1) > Please attach output of: python-updater -p -v -v -v There it is. python-updater extracts RESTRICT_PYTHON_ABIS from ebuilds, but these ebuilds don't set RESTRICT_PYTHON_ABIS and instead inherit gnome-python-common.eclass, which sets RESTRICT_PYTHON_ABIS="3.*". Possible solutions: - Wait for a new EAPI containing appropriate features, which would allow to use USE flags to represent Python ABI dependencies. Then python-updater wouldn't be needed for packages supporting installation for multiple Python ABIs. - Set RESTRICT_PYTHON_ABIS in ebuilds. It would be needed only in current EAPIs. gnome-python-common.eclass could still set RESTRICT_PYTHON_ABIS. I think mass updating ebuilds to set eclass variables before inherit is the right thing to do. *** Bug 348181 has been marked as a duplicate of this bug. *** The appropriate variables are not set in all latest ~arch ebuilds inheriting the eclass. Please reopen if I've missed anything. Thanks for reporting.. (In reply to comment #6) > The appropriate variables are not set in all latest ~arch ebuilds inheriting > the eclass. s/not/now/ :) |