On Mon, Jan 10, 2005 at 06:51:06PM +0100, Frank Küster wrote:
>   set to /var/lib/texmf. Here, "other" means the format files and logs
>   of format generation, the ls-R file for TEXMFMAIN, and the map files
>   generated by updmap.

TEXMFMAIN is also "static" if you set TEXMFVAR and TEXMFCONFIG to
something else. I don't see a need to update the ls-R file of TEXMFMAIN
after the (package) installation.

> - All configuration files must be in /etc because of the FHS, and we
>   achieve this mainly by creating symlinks from TEXMFMAIN to appropriate
>   places below /etc/texmf. There's one more peculiarity: To allow for

To me, these symlinks are just confusing. From all files in TEXMFMAIN,
only texmf.cnf might need tweeking after the installation. So, if I were
you, I'd
  - change the compile time setting of TEXMFCNF to /etc/texmf/web2c
  - patch "make install" to make sure that the texmf.cnf file gets
    installed there
  - set TEXMFVAR, TEXMFCONFIG and VARTEXFONTS before compilation in
    texk/kpathsea/texmf.in via some patch file

>   policy-compliant installation of additional font packages and packages
>   providing additional formats, updmap.cfg and fmtutil.cnf are generated
>   files sitting in /var/lib/texmf/web2c, and the "real" configuration

Just a note: these files belong into the texmf tree pointed at by
TEXMFCONFIG.

>   files from the point of view of users and maintainers of
>   add-on-packages are in /etc/texmf/{fmtutil.d,updmap.d} with Debian
>   scripts generating the files in VARTEXMF.

With teTeX-3.0, modified config files should not be in TEXMFVAR, but
in TEXMFCONFIG.

> - additionally, we are considering to add support for one more tree
>   between TEXMFLOCAL and TEXMFVAR, used for Debian packages that want to
>   override files from teTeX by providing newer versions and that would
>   have a faster release cycle.

That's just fine. Just make an additional dist-tree (choose whatever
name you want, e.g. variablke TEXMFDEBDIST) and set it up in texmf.in
before TEXMFDIST.

> It seems to me now that these locations are kind of orthogonal to what
> you originally intended, so perhaps we should use different names. 

I don't think that it is orthogonal. Some of those settings are just
in line...

Thomas

Reply via email to