This is new, and the basic TeX packages currently transition their files to the new place.
Reasons include hardcoded paths in executables as well as the need for e.g. pool files to exactly match the binaries' version, so that shadowing must be prevented.
Of course this is only a problem if the file is needed in the configure phase. If it is needed only at runtime, a README file to instruct the local admin should be sufficient.
A wishlist bug on the shadowing package, blocked by an other wishlist bug on the basic TeX package, can help tracking these issues.
This allows users to say texdoc packagename directly. Otherwise they will first have to find the right command line (e.g. texdoc packagename/user.dvi) using texdoc -s keyword
Note that in texmf.cnf
, as well as in the sequence of multiple
texmf.cnf
files that are read, earlier entries override later
ones.
However, update-updmap
uses libkpathsea
only in
user-specific-mode. In system-wide mode, it doesn't matter whether
libkpathsea
is configured or not.
An update-updmap
call could take place if another package such as
tetex-bin
is configured in the meantime. That happens sometimes
with APT.
The Debian TeX sub-policy
generated from $Id: Debian-TeX-Policy.sgml 1456 2006-06-25 13:36:29Z frn $debian-tetex-maint@lists.debian.org