Future of LFS - scripts and licenses

Bryan Kadzban bryan at kadzban.is-a-geek.net
Thu May 22 17:08:21 PDT 2008

Hash: RIPEMD160

Bruce Dubbs wrote:
> Bryan Kadzban wrote:
>> I'm not sure if this is possible with the XML toolset, but it may
>> work to grab the values of &udev-config;.tar.bz2 and
>> &udev-config-url;.  Run wget on the second, un-tar the first, and
>> then grab the files from the new directory whose name is the value
>> of &udev-config; on its own.
> Once again please.  I can't parse the above paragraph.

Sorry, let me be more explicit.  I'm going to assume that there's some
command in the XML toolkit (which I'll call "get-entity") that takes an
entity reference's name, and prints the entity's value to stdout.  So
for instance, "get-entity udev-config" would print whatever the entity
&udev-config; expands to in the XML (that is, "udev-config-20080522" in
my current book tree, or "udev-config-20070731 in the current BOOK

The script to build the appendix XML file(s) could then look something
like this:

URL=`get-entity udev-config-url`
DIR=`get-entity udev-config`
wget "$URL"
tar -xf "${DIR}.tar.bz2"
cd "$DIR"
cp *.rules /wherever/BOOK/tmp

and continue on from there like your existing script does, with the sed
to replace ampersands and less-than/greater-than characters, etc.

And of course, the same could work for the bootscripts.

It's still automated, and the appendix is guaranteed to have the same
scripts (or config files) as the book refers to, because we used
general.ent to find the packages, and pulled them from there.  :-)
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the lfs-dev mailing list