Re: external dependencies; trolling for more feedback, pushing to make it official ; -)

J�Thank you for introducing me to yet another GNU/Linux distro. Variety
and innovation are things I truly love about the open source movement.

The issue with HAL-0.5.8.x is one of timing. David jumped the gun by
removing the source code for libvolume_id from HAL. Had he waited a few
months, or rolled up the libvolume_id source into a separate tarball,
there would have never been an issue.

I am currently running HAL- within GARNOME-2.16.x on a PPC
running YDL-4.1 [an FC4 clone]. In order to build HAL, I built udev-100
in a "sandbox" within the GARNOME build environment and manually
extracted the necessary libvolume_id bits. At that time, I noted that I
could automate the extraction process since GARNOME framework supports
"custom" configure, build, and install targets.

As to your suggestion on how to proceed... We do think alike [:-)].
Since there has been such a fuss raised over who should or should not
build libvolume_id, I have revisited automating the extraction of the
libvolume_id bits from udev. A GAR makefile to accomplish this is shown
below.  David, as well as others within the community, should be

Time to move on. There will be other dragons to slay.

Kind regards,



[GAR makefile to biuld and install libvolume_id bits from udev]

GARNAME = udev
CATEGORIES = freedesktop


DESCRIPTION = libvolume_id
define BLURB
Build and extract the libvolume_id bits from udev.



include ../

        @cd $(WORKSRC) && make EXTRAS=extras/volume_id prefix=$(prefix)

        @cd $(WORKSRC) && make -C extras/volume_id prefix=$(prefix) \
                          install-bin install-man


On Fri, 2006-09-22 at 05:44 +0000, J�lleter wrote:
> On Don, 2006-09-21 at 23:09 -0400, Joseph E. Sacco, Ph.D. wrote:
> > GARNOME does not roll or maintain source tarballs for developers. 
> > 
> > I do not know of any stable Linux distro that currently offers a new
> > enough version of udev that provides libvolume_id.  At some point,
> > hopefully in the near future, this will change. Until that time, a
> > source tarball for libvolume_id will need to be made available in order
> > to build HAL-0.5.8.x.
> paldo[1] provides udev-096 in stable (and udev-100 in testing). So now
> you know of one...
> Why can't GARNOME just call these commands in the unpacked udev tarball?
> (possibly adding prefix to the install)
> make EXTRAS="extras/volume_id"
> make -C extras/volume_id/lib install
> J�
> [1]
joseph_sacco [at] comcast [dot] net

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]