This should be simple to resolve. HAL, up through version 0.5.7.1. contained source for libvolume_id. David has decided to remove that source because recent versions of udev provide libvolume_id. The problem is most distros do not yet have a new enough version of udev that provides libvolume_id. Stable releases of the redhat distros are a case in point.
What to do... There are choices... (1) Hal continues to provide libvolume_id for the near term until most major distros provide an acceptable version of udev. (2) A source tarball is created for libvolume_id. There is aleady precedent for this in gnome-mount. Once the distros catch up, this tarball will no longer be required. (3) GNOME apps use HAL-0.5.7.1 until the major distros provide an acceptable version of udev. -Joseph ===================================================================== On Fri, 2006-09-22 at 11:32 +1000, Jeff Waugh wrote: > <quote who="David Zeuthen"> > > > On Thu, 2006-09-21 at 21:21 -0400, Joseph E. Sacco, Ph.D. wrote: > > > GARNOME is a framework for building the GNOME desktop and an assortment > > > of GNOME "extras" using existing source tarballs If a source tarball > > > exists for libvolume_id, GARNOME will use it. If a source tarball for > > > libvolume_id does not exist, GARNOME cannot update HAL past version > > > 0.5.7.1. > > > > So, Joseph, you are saying that limitations in the GARNOME framework means > > that GNOME 2.17/18 is stuck at HAL 0.5.7.1? > > No, he's saying he needs a source tarball. Where's that, so he can integrate > it? > > - Jeff > -- joseph_sacco [at] comcast [dot] net _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
