Jan Nieuwenhuizen writes:
> i would like to keep a copy of the newest stable and the newest
> unstable versions on my computer, so that i can follow and try out and
> contribute to the development of the unstable updates
[..]
> but can switch to a manual install from sources if need be.
If you want to contribute and can build LilyPond yourself, there's no
need to install that development version; you can run it from the
build tree.
I use the (uhm) "attached" scripts to configure and select to use the
lilypond from the local build tree:
$ clily && make
$ . here-lily
We could mention this in the developer corner or in a HACKING file?
Jan.
clily:
#!/bin/bash
[ -x configure ] || ./autogen.sh --noconf
rm -f config.cache
./configure --prefix=$(pwd) --infodir=$(pwd)/share/info --disable-optimising
--enable-gui "$@"
here-lily:
# source me
export PATH=$(pwd)/lily/out:$(pwd)/scripts/out:$PATH
unset LILYPONDPREFIX
unset TEXMF
# ugh: must fool-proof other TeX environment variables
TEXINPUTS=:
MFINPUTS=:
TFMFONTS=:
datadir=$(pwd)/share/lilypond
export TEXMF="{$datadir,"`kpsexpand \\$TEXMF`"}"
export
GS_FONTPATH="$datadir/fonts/type1:/usr/share/texmf/fonts/type1/bluesky/cm:/usr/share/texmf/fonts/type1/public/ec-fonts-mftraced"
export GS_LIB="$datadir/ps:$GS_FONTPATH"
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
