I was reviewing reverse deps of all gnome-common-python bindings and I saw that this package relies on gnome-vfs-python optionally Could then the "python" support be disabled for this? Thanks
I am not sure if I understand your intention correctly. The "python" USE flag is used for assuring that gnome-vfs-python is installed when installing Gnome Commander. Is the removal of "use python && python-single-r1_pkg_setup" in pkg_setup(){...} what you want? Can you give an example of how you would change the ebuild?
It would be to pass --disable-python unconditionally to not RDEPEND on dev-python/gnome-vfs-python Hence, that would also mean to drop the usage of python eclass as no other USE would require it :)
There are some python plugins coming with this package. They are byte-compiled when python is enabled. These plugins therefore need python and also dev-python/gnome-vfs-python. (e.g. /usr/local/lib/gnome-commander/plugins/md5sum.pyc). But I also noticed right now that all plugins crash when executed. (Error message: "Python-Module »gnomevfs« (»gnome.vfs«) could not be loaded"). I have no clue why this is happening currently. But as we have introduced a new plugin system in version 1.6 (not based on python anymore) I am thinking of removing the python support completely. I will provide a new ebuild for this in the next days.
A new version of Gnome Commander is waiting to get into portage. This version (1.8.1) has no python support anymore. I marked this bug here as being dependent on the other one, so if it is fixed, this bug here should be fixed, too.
Meanwhile Gnome Commander 1.8.1 made it into the portage tree, without any python dependency. Because of this I consider this issue as obsolete now.
