Hi thanks, On Thu, May 24, 2012 at 10:35:48AM +0900, Takao Fujiwara wrote: > 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.
This is done. > I think the use of pkg-config is right and I don't understand if your > problem is common in Linux distro. It is not a problem but a suggestion from the bug reporter for more elegant solution to detect python codes. I think we can move on since this pygtk2 modules are not going to be used. > 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. Hmm.. This is more interesting topic. I would like to know timeline with respect to our release schedule so we can plan to include or not to include 1.5 based code for the next release. Debian wheezy freeze is scheduled in June. | A reminder to everyone that the freeze is due in June. The exact | freeze date has not yet been selected. However, if you want your | changes in Wheezy, please be sure to upload them *before* June. > 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. I see... How do we know which related packages are broken by moving to ibus 1.5? 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
