My understanding is your problem can be fixed if Debian ibus has the build dependency of python-dbus-dev. Fedora 16 ibus has the dependencies of dbus-python-devel. I think the use of pkg-config is right and I don't understand if your problem is common in Linux distro.
We are moving not to use pygtk2 for ibus engines so probably I think we won't maintain the ibus pygtk2 modules for now. ibus 1.5 itself has already migrated to use pygobject3 and no longer use dbus-python and the ibus pygtk2 modules are not installed by default in ibus 1.5. E.g. ibus-anthy also don't use pygtk2 in the latest. I hope all ibus engines do not require ibus pygtk2 modules for the long term solution. fujiwara (05/24/12 00:33), Osamu Aoki-san wrote:
Hi, Here is a forwarded wishlist bug report on the build script. Please detect dbus-python via Python (not pkg-config) This is originally discussed at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673853 dbus-python ships a header file and a pkg-config metadata file for use by out-of-tree main loop implementations, such as python-qt4 and python-edbus. These are intended to be pretty rarely used, a lot like python-gtk2-dev - the only packages which are intended to use them are Python bindings for main loop implementations (again, like python-qt4 and python-edbus). Unfortunately, several packages use pkg-config as a more general check for "is dbus-python installed?", and ibus is one of them. This has become significant because the header file and pkg-config metadata have moved to a new binary package, python-dbus-dev. At the moment, python-dbus depends on python-dbus-dev for backwards compatibility (to avoid breaking packages like yours), but I would like to remove that dependency (Bug #673779). -- this is Debian problem and addressed there with some quick fix. Here is a wishlist to upstream by the Debian bug reporter. Longer-term, work being done on pure-Python main loop support might mean that the C header and pkg-config metadata will eventually go away entirely in favour of pure-Python GLib, Qt and E main loop glue. The correct, long-term solution for packages that don't implement a main loop is to check for the dbus Python module (and, if required, the dbus.mainloop.glib Python module) as you would for a pure-Python module: run "python -c 'import dbus'", or use the AM_CHECK_PYMOD macro, or whatever. If you need to check the version number, it's exported by the dbus module as a string (dbus.__version__) and a tuple (dbus.version). Thanks, Osamu
-- You received this message because you are subscribed to the Google Groups "ibus-devel" group. iBus project web page: http://code.google.com/p/ibus/ iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
