[Top][All Lists]

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

Re: Ugliness in the Learning Manual

From: Phil Holmes
Subject: Re: Ugliness in the Learning Manual
Date: Tue, 9 Aug 2011 09:44:04 +0100

----- Original Message ----- From: "Maximilian Albert" <address@hidden>
To: "Phil Holmes" <address@hidden>
Cc: "Graham Percival" <address@hidden>; "David Kastrup" <address@hidden>; <address@hidden>
Sent: Monday, August 08, 2011 9:36 PM
Subject: Re: Ugliness in the Learning Manual

Hi all,

2) list all environment variables used (both internally and
externally) in the build system in the CG.

Advantage: at least this knowledge is written down somewhere.
Disadvantage: the list will not be kept up-to-date. (don't argue;
there's absolutely nothing you can say that will make me believe
that everybody will keep it up-to-date over the next 20 years)

Think it's quite a bit of work, too.

I don't know anything about the build system, but isn't it possible to
do this automatically? Say, if you rename all lilypond-related
environment variables so that they start with LILY_ then why can't you
say something like 'env | grep LILY_' and put the output into the CG?
Please ignore if this doesn't make any sense, I haven't followed the
thread closely so I may be missing something.


The issue arose because texi2pdf has its own environment variable pointing to where texinfo.tex is located. So you have to use the exact name expected by texi2pdf - preceding it with LILY_ would mean it would ignore the variable.

Phil Holmes

reply via email to

[Prev in Thread] Current Thread [Next in Thread]