GNOME Bugzilla – Bug 560927
Add devicekit
Last modified: 2008-12-28 20:12:10 UTC
gnome power manager now uses it
Are tarballs of DeviceKit available?
Created attachment 122732 [details] [review] Patch Only dependency that's missing in libudev. udev is somehow already in jhbuild with libvolume_id but that somehow does not produce libudev? So if anybody knows how to do that the above patch can be applied to get DeviceKit in jhbuild
(In reply to comment #1) > Are tarballs of DeviceKit available? > I just found tarballs of DeviceKit and DeviceKit-power overhere http://hal.freedesktop.org/releases/ Of DeviceKit-disks there does not seem to be tarball yet
I don't think jhbuild should go as deep as udev (as it doesn't make sense to install udev in a different prefix) Also about my request for tarballs, it was because I thought it would be an external dependency for gnome-power-manager, but I just checked and gnome-power-manager connects to DeviceKit through D-Bus (with a helper library, libdevkit-power, which is part of gnome-power-manager); so there is no absolute dependency there, on a first glance.
(In reply to comment #4) > I don't think jhbuild should go as deep as udev (as it doesn't make sense to > install udev in a different prefix) If I'm right DeviceKit needs libudev >= 130, released on 07-Oct-2008. So I think we need to include it in jhbuild, not all distros are using it... > Also about my request for tarballs, it was because I thought it would be an > external dependency for gnome-power-manager Can't we add git checkouts in freedesktop*.modules now and move to tarballs in gnome-external-deps*.module later (when officially approved)?
Created attachment 123496 [details] [review] Take 2 Fix up dependencies, list deps non managed in jhbuild for DeviceKit-disks
Created attachment 123499 [details] [review] Take 3 Removed gyspy cuft from previous patch.
Of course there is no "udev" module in jhbuild... But I hope it will :)
As I wrote previously I don't think it makes sense to install udev in a different prefix; from my point of view the installation and configuration of udev definitely belongs to the distributions, as it is a system thing. I would like to be proved otherwise, you "just" have to explain me how to get udev installed in a different prefix working fine with the distribution-shipped udev.
Richard, could you enlighten me/us?
You need to install udev system-wide. When you've installed 130, DeviceKit should build fine. Once you've got DeviceKit, you can build DeviceKit-power. And you're right -- g-p-m doesn't have a library dep on DeviceKit-power, but if you compile with --enable-devicekit you'll need DeviceKit installed for it to do anything useful.
Thanks for the quick answer Richard. At the moment, on a system without libudev, so no DeviceKit possible, running gnome-power-manager configure script, without any parameter, sets it as DeviceKit-power enabled: DeviceKit-power support: yes So this will make it useless for those people building GNOME with jhbuild. You told me on desktop-devel-list it would be too hard to check at runtime, but what about checking on build time? Would it be possible?
I guess we could check at build time, and look for devkit-gobject. One thing to note -- I'm not building myself the HAL code in trunk, so it might be broken. Long term I want to rip the HAL code out. Richard.
It would really help if it could be checked on build time, do you want a bug report about this?
Request filed against gnome-power-manager as bug 565867. Luca: could you commit your patch, after removing the udev part?
Landed in revision 2605, without udev. http://svn.gnome.org/viewvc/jhbuild/trunk/modulesets/freedesktop-2.26.modules?r1=2546&r2=2605