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.
freddy
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.
-- J5
On Sat, 05 Mar 2005 12:21:04 -0500, John (J5) Palmieri johnp@redhat.com wrote:
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.
Uhm... from the same spec... so far all discussion that I've seen extras/core items need to have seperate srpms. bugzilla does components by srpm with extras and core get seperate listings in bugzilla.
-jef
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@kde.org/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
On Saturday 05 March 2005 18:51, David Zeuthen wrote:
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@kde.org/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
well, just saw it in kdebase/config.log
configure:50348: checking for DBus configure: 50362: /opt/kde/include/dbus/dbus.h configure: 50362: /usr/include/dbus/dbus.h configure: 50362: /usr/local/include/dbus/dbus.h configure: 50362: /usr/include/dbus-1.0/dbus/dbus.h taking that configure: 50379: /opt/kde/include/dbus/dbus-arch-deps.h configure: 50379: /usr/lib/dbus-1.0/include/dbus/dbus-arch-deps.h taking that configure: 50401: /opt/kde/lib/libdbus-1.so configure: 50401: /usr/lib/libdbus-1.so taking that configure:50417: result: headers /usr/include/dbus-1.0 /usr/lib/dbus-1.0/include libraries /usr/lib configure:50430: checking for DBus-Qt bindings configure: 50444: /opt/kde/include/dbus/connection.h configure: 50444: /usr/include/dbus/connection.h configure: 50444: /usr/local/include/dbus/connection.h configure: 50444: /usr/include/dbus-1.0/dbus/connection.h configure: 50444: /usr/local/include/dbus-1.0/dbus/connection.h configure: 50471: /opt/kde/lib/libdbus-qt-1.so configure: 50471: /usr/lib/libdbus-qt-1.so configure: 50471: /usr/local/lib/libdbus-qt-1.so configure:50491: result: searched but not found configure:50501: checking if the HAL backend for media:/ sould be compiled configure:50516: result: no
freddy
On Sat, 2005-03-05 at 12:51, David Zeuthen wrote:
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@kde.org/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
In which case someone needs to do the work of getting the Qt-dbus bindings up to par and KDE ported before I will consider enabling it. I don't know if I will feel comfortable enabling it until D-BUS goes 1.0 (which should be soon). Note that by Monday D-BUS 0.3.0 will be in rawhide.
-- J5
On Sat, 2005-03-05 at 12:59 -0500, John (J5) Palmieri wrote:
In which case someone needs to do the work of getting the Qt-dbus bindings up to par and KDE ported before I will consider enabling it.
Certainly.
I don't know if I will feel comfortable enabling it until D-BUS goes 1.0 (which should be soon).
If it's actively maintained and it works, it shouldn't be different from other bindings we ship though.
Note that by Monday D-BUS 0.3.0 will be in rawhide.
No, that would be 0.30cvssomething cause the python bindings since 0.30 needed some work - someone really ought to do a real D-BUS release before then so we don't have to ship a CVS snapshot.
David
On Sat, 2005-03-05 at 13:08, David Zeuthen wrote:
On Sat, 2005-03-05 at 12:59 -0500, John (J5) Palmieri wrote:
In which case someone needs to do the work of getting the Qt-dbus bindings up to par and KDE ported before I will consider enabling it.
Certainly.
I don't know if I will feel comfortable enabling it until D-BUS goes 1.0 (which should be soon).
If it's actively maintained and it works, it shouldn't be different from other bindings we ship though.
Note that by Monday D-BUS 0.3.0 will be in rawhide.
No, that would be 0.30cvssomething cause the python bindings since 0.30 needed some work - someone really ought to do a real D-BUS release before then so we don't have to ship a CVS snapshot.
Ya, ya ;-) I'm going to try to do a release today but like I said the qt bindings aren't passing dist check so I'll ask on the dbus list about them and see what their status is. Was hoping Joe was going to do this but he probably ran into the same problems I did and didn't have time to resolve them.
-- J5
John (J5) Palmieri wrote:
On Sat, 2005-03-05 at 11:37, Frederick Alexander Thomssen wrote:
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?
k3b (v0.12+), at least, can use it, if available.
-- Rex
Rex Dieter wrote:
John (J5) Palmieri wrote:
On Sat, 2005-03-05 at 11:37, Frederick Alexander Thomssen wrote:
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?
k3b (v0.12+), at least, can use it, if available.
For the record, I've hacked dbus.spec to re-enable Qt support, updating references to Qt 3.1 to 3.3).
The resulting dbus-qt subpackage builds and installs correctly. KDE builds fine against it with a small configury patch to look for libraries in /usr/lib64 on x86_64.
Now I can use media:/ in Konqueror. Looks like a safe change for fedora-devel.
Bernardo Innocenti wrote:
Rex Dieter wrote:
John (J5) Palmieri wrote:
On Sat, 2005-03-05 at 11:37, Frederick Alexander Thomssen wrote:
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?
k3b (v0.12+), at least, can use it, if available.
For the record, I've hacked dbus.spec to re-enable Qt support, updating references to Qt 3.1 to 3.3).
The resulting dbus-qt subpackage builds and installs correctly. KDE builds fine against it with a small configury patch to look for libraries in /usr/lib64 on x86_64.
Now I can use media:/ in Konqueror. Looks like a safe change for fedora-devel.
As of today dbus-qt is still disabled in Fedora. The attached patch is enough to get it to build.
I've rebuilt KDE from CVS and I can confirm media:/ works and removable devices are correctly detected, but not automounted.
Will build it in rawhide on monday.
On Sat, 2005-08-13 at 23:43 +0200, Bernardo Innocenti wrote:
Bernardo Innocenti wrote:
Rex Dieter wrote:
John (J5) Palmieri wrote:
On Sat, 2005-03-05 at 11:37, Frederick Alexander Thomssen wrote:
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?
k3b (v0.12+), at least, can use it, if available.
For the record, I've hacked dbus.spec to re-enable Qt support, updating references to Qt 3.1 to 3.3).
The resulting dbus-qt subpackage builds and installs correctly. KDE builds fine against it with a small configury patch to look for libraries in /usr/lib64 on x86_64.
Now I can use media:/ in Konqueror. Looks like a safe change for fedora-devel.
As of today dbus-qt is still disabled in Fedora. The attached patch is enough to get it to build.
I've rebuilt KDE from CVS and I can confirm media:/ works and removable devices are correctly detected, but not automounted.
-- // Bernardo Innocenti - Develer S.r.l., R&D dept. \X/ http://www.develer.com/
devel@lists.stg.fedoraproject.org
-
Bernardo Innocenti -
David Zeuthen -
Frederick Alexander Thomssen -
Jef Spaleta -
John (J5) Palmieri -
Rex Dieter