On Sat, 2005-03-05 at 12:21 -0500, John (J5) Palmieri wrote: >On Sat, 2005-03-05 at 11:37, Frederick Alexander Thomssen wrote: >> hi, >> >> once dbus-qt was removed from fedora because there was no use for it. but now >> kde 3.4 supports dbus-qt for the media:/ protocol which indicated if a new >> device was connected. so there now is a use for dbus-qt so i think it ought >> to be included. > >Does an app in fedora core require it? When you say the media:/ >protocol indicates if a new device is connected, does it listen to dbus >signals or does it propagate them itself? For device connection there >is already a freedesktop standard for propagating device additions and >removals called HAL. Also does kde 3.4 compile against the qt-dbus >bindings in CVS? So far the qt bindings in CVS have not been passing a >dist check on my fedora box. This may be a candidate for extras if I >can figure out how to split packages between extras and core when they >come from the same spec. I also have no objection into getting into >core provided there is a real need. I am hesitant to put it in if the >API is still in flux since the apps that use it and the version of dbus >we ship may get out of sync. It appears to use hal 0.4.x and dbus 0.23.x cf. http://www.archivum.info/kde-core-devel@xxxxxxx/2004-12/msg00290.html If the Qt bindings for D-BUS 0.30 is/gets in a usable state, we should look at writing a patch so it can speak to hal 0.5.x - it shouldn't be much work at all; updating the Qt D-bindings to the new D-BUS is the big thing that needs to work. David
