> > > On Wed, 26 Jun 2002, Jan Nieuwenhuizen wrote: > > > Mats Bengtsson <[EMAIL PROTECTED]> writes: > > > > > This is nonsence. If the TEXMF variable doesn't include > > > the default teTeX texmf tree, TeX or LaTeX won't be able > > > to find any of the standard package files. > > > > Oops. So, make that: > > > > TEXMF="{$(pwd)/lilypond/share/lilypond/<version>, $(kpsexpand \$TEXMF)}" > > > > That will not work either. The problem is, that on some distributions > TEXMF is not at all set, but tex will still find its own files (I guess > by evaluating $0 from the invoking shell before actually running tex). > However, *if* TEXMF is set to some value, it must include the tex > installation path.
It does work (at least if you use this method to point to the installation directory). The trick is that 'kpsexpand \$TEXMF' reads the value from texmf.cnf if the environment variable $TEXMF is undefined. This is exactly the method used in Lilypond since 1.5.4x. > > > Use a setting similar to the one in buildscripts/out/lilypond-profile > > > instead. > > > > Yes, but I just wanted to mention that (wrong) TEXINPUTS, TFMFONTS, > > MFINPUTS, override a (correct) TEXMF and still break things. > > > > > Also, since the build directory doesn't match the > > > standard TeX directory structure (see `texdoc tds`), > > > tex/latex won't find any of the font files or other > > > necessary files. > > > > How is that? .62/latest CVS should create a valid tds in the build > > directory, but I'm not a guru at this (as my prev post also shows). > > > > Jan. > > I am neither a TeX guru, but my TEXMF has to include at least both, > the <install_dir>/share/lilypond/1.5.63/fonts *and* the > <install_dir>/share/lilypond/1.5.63/fonts/afm directory (and probably > also the fonts/source directory, if the fonts have not yet been compiled) > to work. So I guess, there is something wrong with the directory > structure. Yes, the build directory is definitely not according to TDS. > I also would prefer a structure of the form > <install_dir>/share/lilypond-1.5.63 rather than > <install_dir>/share/lilypond/1.5.63, because with the former I ran into > difficulties when using symlinks: I made a symlink "1.5.63 -> .", and > "/usr/share/<directory_where_lily_fonts_usually_go> -> > /home/reuter/lilypond/share/lilypond" and "/home/reuter/lilypond -> > <install_dir>". This made (until 1.5.58) it possible to change between > various lilypond installations on the fly by just changing the single link > /home/reuter/lilypond to point to the current version. However, the > symlink "1.5.63 -> ." turned out to be harmful, because the next time the > tex file database is automatically updated, this leads to endless > recursive file path. As a result, I got a huge cache file in the texmf/db > directory (ca. 20MB), which caused a delay of a some minutes each time > invoking any tex related command... What I have done is to run directly from the build directory, using a local texmf-like directory with soft links to the corresponding directories in the build directory. As a starting point, I use a directory structure as described in http://lilypond.org/wiki/?MakingPatches with a soft link 'lilypond' pointing to the build directory of the current version. In the directory above the build directories, I also have a directory 'localtexmf' with the following contents: localtexmf/dvips -> ../lilypond/mf/out/ localtexmf/fonts/source -> ../../lilypond/mf/ localtexmf/fonts/afm -> ../../lilypond/mf/out/ localtexmf/fonts/pk -> ../../lilypond/mf/out/ localtexmf/fonts/tfm -> ../../lilypond/mf/out/ localtexmf/fonts/type1 -> ../../lilypond/mf/out/ localtexmf/tex/ localtexmf/tex/fetadefs -> ../../lilypond/mf/out/ localtexmf/tex/tex -> ../../lilypond/tex/ where '->' denotes a soft link. With this setup, I can easily change between versions by just moving the single link 'lilypond'. /Mats _______________________________________________ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel