The attached patches add support for installation for multiple Python versions. Previous versions of dev-python/pygobject were installing libpyglib-2.0-python.so which is used by dev-python/pygobject modules installed in site-packages directory which is specific to given Python version. Sources of libpyglib-2.0-python.so use headers specific to given Python version. libpyglib-2.0-python.so must be renamed to allow safe using of it by dev-python/pygobject modules. libpyglib-2.0-python.so seems to be a private library, so renaming shouldn't cause any problems. dev-python/pygtk belongs to python herd, so we can fix dev-python/pygtk. I would like to ask for permission to fix dev-python/pygobject. This bug blocks farther convertion of ebuilds of many packages depending on dev-python/pygobject or dev-python/pygtk, so it needs to be fixed quickly.
Created attachment 202362 [details, diff] pygobject-2.18.0-r1.ebuild.patch
Created attachment 202363 [details, diff] pygobject-2.18.0-support_multiple_python_versions.patch
Created attachment 202365 [details, diff] pygtk-2.14.1-r2.ebuild.patch
Fixed.
I have no idea of what is the use of such change really. Plus it seems worthless effort since no gnome ebuild respects eselected-python currently... Please enlighten me.
(In reply to comment #5) > it seems worthless effort since no gnome ebuild respects eselected-python > currently... There are some packages (e.g. dev-python/pywebkitgtk-1.1.6) which depend on dev-python/pygtk:2 and support installation for multiple Python versions. (Functionality provided by new versions of eselect-python (respecting of EPYTHON variable) is currently used only by some important code inside python.eclass. Ebuilds rather always should use appropriate functions from python.eclass instead of manually setting EPYTHON variable.) A draft of conversion guide will ready soon.
I hope you are going to make this stuff easier to use because I am currently greatly dissatisfied with the increase in complexity it drops down on us.
