[Top][All Lists]

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

Re: lilypond-book

From: Mats Bengtsson
Subject: Re: lilypond-book
Date: Wed, 16 Mar 2005 18:07:32 +0100
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)

Han-Wen Nienhuys wrote:
address@hidden writes:

make[1]: Entering directory `/usr/src/lilypond'
*** Before using LilyPond, the contents of one of the login scripts
*** buildscripts/out/lilypond-{profile,login} should be sourced.
*** LilyPond should have been installed to do that automatically
*** when you log in.  So, please log out now and log in again.
*** For more information see Invoking LilyPond in the manual.
make[1]: Leaving directory `/usr/src/lilypond'

Sorry, that message is totally crap.

Also, it is largely irrelevant now that we have fontconfig support.

Graham, can you make sure that the right setting for TEXMF for TeX
support is described in the manual? Once it's working, we can simply
scrap these scripts.

What do you mean? There's no point in telling people that the correct
value of TEXMF is '{/usr/share/lilypond/2.5.15,{/home/hankwang/texmf,!!/usr/local/share/texmf,!!/usr/share/texmf}}'
for example, since the correct setting on my machine is completely
different, so we cannot easily get rid of lilypond-profile. Also, the
solution of making sure that the file is installed in /etc/profile.d/ is
relevant on some systems but not on Debian, for example.
My conclusion is that the best solution is that every package makes sure
to either install lilypond-profile in a relevant place or install the
LilyPond files into an existing texmf tree (the current Debian
solution). In other words, you shouldn't have to bother if you install
from a package. For people compiling from source code, I afraid they
have to be prepared to read the INSTALL.txt. Maybe we could improve
their situation slightly by telling the short story in the beginning
of INSTALL.txt:
Run configure
Run make
Run make install
Make sure that lilypond-profile is copied to a place where it's sourced.
and then giving the current long story with all the details.
I've seen this approach in the INSTALL.txt file for many programs.


reply via email to

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