Re: cygwin: lilypond and tetex-3.0
Thomas Esser writes: Hmm. Maybe, in texmf.cnf, TEXMFVAR must be added to SYSTEXMF SYSTEXMF works for what it is good for: to decide if some font source comes from a system tree. Texmf.cnf says about SYSTEXMF % The system trees. These are the trees that are shared by all the users. The font cache (VARTEXFONTS) is set to /var/cache/fonts. Don't list TEXMFVAR in SYSTEXMF. Why must TEXMFVAR (=/var/lib/texmf) drwxr-xr-x 4 root root 4096 2004-12-20 22:47 /var/lib/texmf drwxr-xr-x 2 root root 4096 2004-12-27 17:39 /var/lib/texmf/web2c/ a read-only tree for all users, not be part of SYSTEXMF? Why is this bad? It seemed to work, and it is what Debian does too. Can you suggest a better variable to add TEXMFVAR to? I often look at Debian's solutions, as they are usually quite good at following and implementing the FHS. This is the sort of decision that I'm quite uncomfortable about. I would like to keep upstream's defaults, but I also want to have a standards compliant system. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: cygwin: lilypond and tetex-3.0
Frank Küster writes: Maybe SYSTEXMF should be renamed to TEXMFSYSFONTS? Hm, which version of teTeX in Debian do you mean? For the 3.0 packages, neither TEXMFVAR nor TEXMFSYSVAR will be in TEXMFSYS. Ah, I see, there were some major changes after 2.99.7 that I haven't introduced into my texmf.cnf. I did not expect any changes and did not check for them. I will have a careful look into this. To be bold, this unbelievable flexibility confuses me. I am wondering what the plusses are to have a more complex texmf.cnf than say, for root CONFIG: /etc/texmf/ STATIC: /usr/share/texmf/ DYNAMIC: /var/lib/texmf/ and for users FONTS:/var/cache/fonts/ Then duplicate the lot for the user's $HOME directory. I have not yet, as a packager nor as user, felt the need for much more than that. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: cygwin: lilypond and tetex-3.0
Bertalan Fodor writes: I've found the problem, but I'm still not sure in solution: there is an mf.base file in /usr/share/texmf/web2c That's strange. But texconfig creates its formats in /var/lib/texmf/web2c That's correct. So mf looks at the wrong place for mf.base Can you find out why that is? What does kpsewhich mf.base say? Do you have the new versions of texmf.cnf (the 3.0 version has TEXMFVAR, previous versions have VARTEXMF). Hmm. Maybe, in texmf.cnf, TEXMFVAR must be added to SYSTEXMF TEXMFVAR = /var/lib/texmf .. %%SYSTEXMF = $TEXMFLOCAL;$TEXMFMAIN;$TEXMFDIST SYSTEXMF = $TEXMFLOCAL;$TEXMFVAR;$TEXMFMAIN;$TEXMFDIST Shouldn't mf.base and the other format files generated into /usr/share/texmf/web2c? No, the FHS dictates generated stuff to go in /var, /usr may be read-only. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org
Re: cygwin: lilypond and tetex-3.0
Thanks for suggesting looking at texmf.cnf
I've found the following:
TEXMFMAIN = /usr/share/texmf
TEXMFCONFIG = $TEXMFMAIN
% - make sure that $TEXMFVAR precedes $TEXMFMAIN in the TEXMF definition.
TEXMF =
{!!$TEXMFCONFIG,!!$TEXMFVAR,!!$TEXMFMAIN,$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFDIST}
As you can see TEXMFCONFIG is equal to TEXMFMAIN, so TEXMFVAR is not
before TEXMFCONFIG. So changing the line to
TEXMF =
{!!$TEXMFVAR,!!$TEXMFCONFIG,!!$TEXMFMAIN,$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFDIST}
solves the problem.
Bert
