(In reply to comment #44)
> > Is it possible to use GDbus without GLib main loop?
>
> No, it runs using gio which is tied to the mainloop for async io. There is
> integration between Qt and the glib mainloop but I'm not sure it works or not.
FWIW, Qt/GLib main loop integration does work: Qt4 in Debian (and derivatives, like Ubuntu) is compiled with it enabled, and we use it for telepathy-qt4's regression tests, in which QtDBus clients talk to dbus-glib services in the same process.
(In reply to comment #45)
> Making dbus depend on Gnome doesn't seem like a good approach for KDE users.
Making dbus-python (a subset of D-Bus) depend on GLib (a library used by GNOME) isn't the same thing as making D-Bus depend on GNOME. As a result of the main-loop integration, Qt (and hence KDE) on Debian/Ubuntu already depends on GLib.
(In reply to comment #44)
> > Is it possible to use GDbus without GLib main loop?
>
> No, it runs using gio which is tied to the mainloop for async io. There is
> integration between Qt and the glib mainloop but I'm not sure it works or not.
FWIW, Qt/GLib main loop integration does work: Qt4 in Debian (and derivatives, like Ubuntu) is compiled with it enabled, and we use it for telepathy-qt4's regression tests, in which QtDBus clients talk to dbus-glib services in the same process.
(In reply to comment #45)
> Making dbus depend on Gnome doesn't seem like a good approach for KDE users.
Making dbus-python (a subset of D-Bus) depend on GLib (a library used by GNOME) isn't the same thing as making D-Bus depend on GNOME. As a result of the main-loop integration, Qt (and hence KDE) on Debian/Ubuntu already depends on GLib.