FS#4493 - gnome-python-desktop should depend on libwnck
Attached to Project:
Arch Linux
Opened by Tom Killian (tomk) - Saturday, 22 April 2006, 09:24 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 24 April 2006, 17:10 GMT
Opened by Tom Killian (tomk) - Saturday, 22 April 2006, 09:24 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 24 April 2006, 17:10 GMT
|
Details
gnome-python-desktop provides
/usr/lib/python2.4/site-packages/gtk-2.0/wnck.so, but python
cannot import it unless libwnck is also installed. Here's a
relevant error:
Traceback (most recent call last): File "/usr/bin/foopanel", line 37, in ? foopanel.run() File "/usr/lib/python2.4/site-packages/foopanel/__init__.py", line 86, in run globals.config.gui = core.ConfDialog() File "/usr/lib/python2.4/site-packages/foopanel/lib/core.py", line 480, in __init__ self.__set_values_to_gui() File "/usr/lib/python2.4/site-packages/foopanel/lib/core.py", line 541, in __set_values_to_gui self.__init_pluginview() File "/usr/lib/python2.4/site-packages/foopanel/lib/core.py", line 580, in __init_pluginview self.__parse_plugin( t ) File "/usr/lib/python2.4/site-packages/foopanel/lib/core.py", line 559, in __parse_plugin exec( "import plugins.%s as plugin" % t ) File "<string>", line 1, in ? File "/usr/lib/python2.4/site-packages/foopanel/plugins/pager/__init__.py", line 37, in ? import wnck ImportError: libwnck-1.so.18: cannot open shared object file: No such file or directory In this case, my workaround is to make foopanel depend on libwnck, but that doesn't solve the problen for any other app that wants to use /usr/lib/python2.4/site-packages/gtk-2.0/wnck.so. |
This task depends upon
- libwnck
- totem-plparser
- nautilus-cd-burner
- metacity
- gnome-media
- libgtop
- gtksourceview
- libgnomeprint
- gnome-applets
The reason to not depend on all these things is simple: just think about the fact that your application wants to use printing, so it imports the gnomeprint bindings from gnome-python-desktop. Then your application depends on all these other packages, which makes your application "bloated" in the eyes of the "I don't want that G*-thing on my system" user. The workaround is to depend on the libraries for which you need the bindings.
OTOH, it's good to know that my workaround gets the official thumbs-up. :P