Discussion: is building X.org from source now a joke?

Simon Geard delgarde at ihug.co.nz
Fri Feb 29 01:02:15 PST 2008

On Thu, 2008-02-28 at 13:34 -0500, john q public wrote:
> I was lazy I just grabbed the lists of names in order from the BLFS site 
> reduced them to basenames with sed and did the
> following:
> for modname in `cat modules-list`;do cd $modname*;<whatever I needed to 
> cut and paste from BLFS>;cd ..;done

See, that's the first step as far as I'm concerned. Start with a little
scripting to simplify the install process, and you quickly become pretty
good at scripting, ending up with most of the BLFS process automated.

In my case, there's about 400 lines of Python code which reads a bunch
of per-package instruction files. And it's really not all that hard to
maintain, since most packages are exactly the same apart from a few
config parameters. So individual instructions typically end up looking
something like:


or for a slightly non-standard case:

    custom_make=('make -f unix/Makefile generic_gcc',),
    custom_install=('make -f unix/Makefile prefix=/usr install',)

which behind the scenes are translated into the actual build
instructions (in the form of a 8000+ line auto-generated Makefile).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxfromscratch.org/pipermail/blfs-support/attachments/20080229/680ade2a/attachment.sig>

More information about the blfs-support mailing list