On Fri, 2009-12-04 at 00:52 +0100, Arvid Picciani wrote: > Pierre Chapuis wrote: > > > Take gedit for example. It is a text editor, and: > > > > [23:44 TA|catwell] ldd $(which gedit) | grep dbus > > libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x00007f5df48bb000) > > libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f5df467c000) > > > > AFAIK it uses dbus only to communicate with itself (between its instances). > > There is no iteroperability problem, so D-Bus is not that useful to me. > > But then again, maybe I don't know how gedit works well enough to judge... > > > > > funny thing: gedit is the first time i noticed the problem. > then i went emacs, and now emacs depends on dbus. > What does upstream have to say about this dependency? Does not seem 'necessary' to me, but depending on the app's structure the choice could be between:- a) some new feature which requires dbus b) not having the feature Which would then lead to the question whether the app's design allows dbus to be loaded only when necessary instead of linked at compile-time. I doubt many apps are designed to allow dbus to be used 'if and only if available' at run-time?
