[tex-live] Re: Bizarre perforce situation

[Olaf Weber]

Thomas Esser writes:

>> % The tree containing the runtime files closely related to the specific
>> % program version used:
>> TEXMFMAIN = @texmf@
>> 
>> % The main distribution tree:
>> TEXMFDIST = @texmf at -dist
>> 
>> ...
>> 
>> TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN,!!TEXMFDIST}

> A $ is missing before TEXMFDIST and one line needs to be added to
> texk/kpathsea/Makefile.in:

> --- old/Makefile.in   Sat Feb 15 14:55:19 2003
> +++ ./Makefile.in       Sat Feb  7 22:54:57 2004
> @@ -78,6 +78,7 @@
>  # likely to have been mangled as well.
>         echo '/^ *TEXMFMAIN[ =]/s%\$$TEXMF%$(texmf)%' >>$@
>         echo '/^[% ]*TEXMFLOCAL[ =]/s%\$$TEXMF%$(texmf)%' >>$@
> +       echo '/^[% ]*TEXMFDIST[ =]/s%\$$TEXMF%$(texmf)%' >>$@
>         echo '/^[% ]*VARTEXMF[ =]/s%\$$TEXMF%$(texmf)%' >>$@
>         echo '/^[% ]*TEXMFCNF[ =]/s%\$$TEXMF%$(texmf)%' >>$@
>  # And fill in the last clause of TEXMFCNF with an absolute path.

Something else is missing as well: TEXMFDIST must be added to
SYSTEXMF.  Arguably, using VARTEXMF instead of TEXMFMAIN to store
formats is better.  Arguably, it is not, if you consider VARTEXMF to
be volatile in the sense of "delete-when-convenient".

Index: texmf.in
===================================================================
RCS file: /usr/local/cvsroot/texk/texk/kpathsea/texmf.in,v
retrieving revision 1.56
diff -u -d -r1.56 texmf.in
--- texmf.in    4 Jan 2004 17:00:45 -0000       1.56
+++ texmf.in    8 Feb 2004 17:34:51 -0000
@@ -74,10 +74,10 @@
 %   - list $VARTEXMF in the TEXMF definition;
 %   - make sure that $VARTEXMF precedes $TEXMFMAIN in the TEXMF definition.
 % TEXMF = $TEXMFMAIN
-TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN}
+TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN,!!$TEXMFDIST}

 % The system trees.  These are the trees that are shared by all the users.
-SYSTEXMF = $TEXMFLOCAL:$TEXMFMAIN
+SYSTEXMF = $TEXMFLOCAL;$TEXMFMAIN;$TEXMFDIST

 % Where generated fonts may be written.  This tree is used when the sources
 % were found in a system tree and either that tree wasn't writable, or the
@@ -100,7 +100,7 @@
 % or mktexlsr will generate an ls-R file for $HOME when called, which is
 % rarely desirable.  If you do this you'll want to define SYSTEXMF like
 % this:
-%   SYSTEXMF = $TEXMFLOCAL;$TEXMFMAIN
+%   SYSTEXMF = $TEXMFLOCAL;$TEXMFMAIN;$TEXMFDIST
 % so that fonts from a user's tree won't escape into the global trees.
 %
 % On some systems, there will be a system tree which contains all the font

-- 
Olaf Weber

               (This space left blank for technical reasons.)