Even after a previous successful run, python-updater updates these packages again:
[ebuild R ] dev-python/libgnomecanvas-python-2.28.1 USE="-examples" 0 kB
[ebuild R ] dev-python/gconf-python-2.28.1 USE="-examples" 0 kB
[ebuild R ] dev-python/gnome-vfs-python-2.28.1 USE="-doc -examples" 0 kB
[ebuild R ] dev-python/libbonobo-python-2.28.1 USE="-examples" 0 kB
[ebuild R ] dev-python/gtkmozembed-python-2.25.3 USE="-debug -doc" 0 kB
[ebuild R ] dev-python/libgnome-python-2.28.1 USE="-examples" 0 kB
It does so even when called with --disable-manual. Is that expected?
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.*".
- 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.