[tex-live] texmf.cnf-4WIN

Reinhard Kotucha reinhard.kotucha at web.de
Thu Feb 15 22:49:20 CET 2007

>>>>> "Frank" == Frank Küster <frank at kuesterei.ch> writes:

  > Reinhard Kotucha <reinhard.kotucha at web.de> wrote:
  >> you'll see that it first looks for
  >> /path/to/texlive/bin/<platform>/texmf.cnf
  >> Obviously it's best to create a file "Master/bin/win32/texmf.cnf"
  >> which only contains things which are supposed to be different on
  >> Windows.
  >> This has many advantages:
  >> 1. Changes made in the main texmf.cnf file will be taken into
  >> account immediately.  Only variables you changed will not be
  >> affected.

  > And that might again lead to problems, in particular if we forgot
  > that a variable that we want to change is set differently on
  > Windows.

There are only a few variables which differ from the main texmf.cnf.
Since Staszek wants to get rid of the *-sys programs he commented out
a few variables.  He also had to add new stuff for XeTeX because there
usually are no config files for fontconfig on Windows.

What we have in TeXLive for Windows is that:  All *-sys programs had
been removed and all variables "*SYS*" had been commented out in
texmf.cnf.  If no *-sys programs are available there is no need to
remove "*SYS*" variables because there is no program which uses them.

But maybe there is a better solution.  I suppose that what Staszek
really wants is to avoid that foo{,-sys} write files to different
directories.  Since getnonfreefonts depends on -sys we currently have

Doesn't it make sense to treat all the other variables similar?  The
*-sys programs can be retained then but it doesn't make any difference
whether you say updmap or updmap-sys, files are written to the same

But if you remove/rename bin/win32/texmf.cnf your system will find the
genuine texmf.cnf.

  > Why not try to generate the texmf.cnf for windows at build time?
  > It is generated anyway, from texmf.in (I guess this is the same
  > when building for windows?), and we could apply an additional sed
  > script to make the win-specific changes.  If we code carefully,
  > any change to texmf.in in lines with windows-specific settings
  > will cause the Win-ify sed script to fail, and we won't forget to
  > think about it and adapt it.

Actually texmf.in is not used at all.  What we have in TeXLive is
Master/texmf/web2c/texmf.cnf.  Though Karl tries to keep texmf.in
up-to-date, these files are maintained separately.  It would be nice
to derive texmf.cnf from texmf.in because some people might want to
configure --without-multiplatform.


Reinhard Kotucha			              Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha at web.de
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.

More information about the tex-live mailing list