On Thu, 15 Jul 1999, Han-Wen Nienhuys wrote:
> > the MFINPUTS variable, metafont writes pk files into the current
> > working directory when xdvi is called.
> >
> > When I unset the MFINPUTS variable and put a link from
> > /usr/local/share/lilypond/mf to
> > /usr/share/texmf/fonts/source/lilypond, metafont writes the pk files
> > to /var/lib/texmf/pk.
>
> We used to have such a scheme, but it has some problems:
>
> * You need to be root (This is no problem on your own GNU box) for
> this to work, and
Okay, you could have a --disable-root configure option or
something. If you want to install Lilypond as non-root, you'll have to
give a --prefix option anyway. Besides, root installation is probably
the most often used option, so this is, IMHO, not an argument.
> * Detecting where to put the symlink is a complete pain in the arse.
Well, you already detect where cmr10.mf lives, so that shouldn't be a
big problem.
> * I don't think it is good policy to muddle with the directory
> structure of a different package (in this case, tetex).
Hmm. This is of course not nice. What about an optional "make
modify-tex" Makefile rule. The two options could be mentioned in the
INSTALL file then. Give the user the choice.
> The current situation is not perfect, but it makes installing Lilypond
> a no-brainer.
Not quite. From the INSTALL file it's not perfectly clear that you
have to source the profile script to setup the $MFINPUTS and
$TEXINPUTS variables. At least I had this problem when I first tried
Lilypond, and I tried setting the symlinks, which worked.
> Are there any TeX gurus with good ideas on this ?
No way :)
--
michael krause [aka raw style / lego] - www.tu-harburg.de/~semk2104/
