Bug#93781: tetex-bin: texdoc
Package: tetex-bin
Version: 1.0.6-7
Severity: wishlist
I have a problem with texdoc. E.g.: I have 2 different versions of
usrguide installed on my machine. One is in the original texmf-tree.
The other is the *updated* version and is located in the local
texmf-tree. My $TEXMFLOCAL is defined, in the search path before the
$TEXMFMAIN und updated using texhash.
The usrguide, which comes with the dist, is compressed using
dh_compress, while the usrguide in the local tree is not. The
texdoc-script by Thomas Esser is modified to look up first for
compressed docu and handle it. Therefore "texdoc -l usrguide" gives
me first the old usrguide in the dist-texmf-tree and then the local
updated version. When I type "texdoc usrguide" the script presents me
the old version, but I would like the get the local (new) one.
The best solution, I see in the moment is to shuffle around the
line in the texdoc script and search for the compressed docu after
the uncompressed in my local tree. i.e.:
listext='.dvi:.pdf:.ps:.txt:.dvi.gz:.pdf.gz:.ps.gz:.txt.gz:.html:""'.
This method will only fail, if the dist-version is not compressed,
while the local is and if the local tree is searched after the
dist-tree.
Hilmar
-- System Information
Debian Release: 2.2
Linux rudi 2.2.19 #2 Thu Mar 29 12:44:32 CEST 2001 sparc unknown
libc6 (>= 2.1.2), libpng2, libstdc++2.10, libz1, tetex-lib (>=
1.0.6-6), xlib6g, xlib6g (>= 3.3.6), tetex-lib (>= 1.0.6), tetex-base
(>= 1.0-5), ed, debianutils (>= 1.13.1)
% original texmf.cnf -- runtime path configuration file for kpathsea.
% (If you change or delete `original' on the previous line, the
% distribution won't install its version over yours.)
% Public domain.
%
% What follows is a super-summary of what this .cnf file can
% contain. Please read the Kpathsea manual for more information.
%
% texmf.cnf is generated from texmf.in, by replacing @var@ with the
% value of the Make variable `var', via a sed file texmf.sed, generated
% (once) by kpathsea/Makefile (itself generated from kpathsea/Makefile.in
% by configure).
%
% Any identifier (sticking to A-Za-z_ for names is safest) can be assigned.
% The `=' (and surrounding spaces) is optional.
% No % or @ in texmf.in, for the sake of autogeneration.
% (However, %'s and @'s can be edited into texmf.cnf or put in envvar values.)
% $foo (or ${foo}) in a value expands to the envvar or cnf value of foo.
%
% Earlier entries (in the same or another file) override later ones, and
% an environment variable foo overrides any texmf.cnf definition of foo.
%
% All definitions are read before anything is expanded, so you can use
% variables before they are defined.
%
% If a variable assignment is qualified with `.PROGRAM', it is ignored
% unless the current executable (last filename component of argv[0]) is
% named PROGRAM. This foo.PROGRAM construct is not recognized on the
% right-hand side. For environment variables, use FOO_PROGRAM.
%
% Which file formats use which paths for searches is described in the
% various programs' and the kpathsea documentation.
%
% // means to search subdirectories (recursively).
% A leading !! means to look only in the ls-R db, never on the disk.
% A leading/trailing/doubled ; in the paths will be expanded into the
% compile-time default. Probably not what you want.
%
% You can use brace notation, for example: /usr/local/{mytex:othertex}
% expands to /usr/local/mytex:/usr/local/othertex. Instead of the path
% separator you can use a comma: /usr/local/{mytex,othertex} also expands
% to /usr/local/mytex:/usr/local/othertex. However, the use of the comma
% instead of the path separator is deprecated.
%
% The text above assumes thet path separator is a colon (:). Non-UNIX
% systems use different path separators, like the semicolon (;).
% Part 1: Search paths and directories.
% You can set an environment variable to override TEXMF if you're testing
% a new TeX tree, without changing anything else.
%
% You may wish to use one of the $SELFAUTO... variables here so TeX will
% find where to look dynamically. See the manual and the definition
% below of TEXMFCNF.
% The main tree, which must be mentioned in $TEXMF, below:
TEXMFMAIN = /usr/share/texmf
% A place for local additions to a "standard" texmf tree. For example:
TEXMFLOCAL = /usr/share/texmf.local
% If defined, teTeX's texconfig stores modifications here (instead of the
% TEXMFMAIN tree).
% VARTEXMF = /usr/share/texmf-var
% User texmf trees can be catered for like this...
% HOMETEXMF = $HOME/texmf
% Now, list all the texmf trees. If you have multiple trees you can
% use shell brace notation, like this:
TEXMF = {!!$TEXMFLOCAL,!!$TEXMFMAIN}
% The braces are necessary. If you set VARTEXMF, you also have to
% - list $VARTEXMF in the TEXMF definition;
% - make sure that $VARTEXMF precedes $TEXMFMAIN in the TEXMF definition.
% TEXMF = !!$TEXMFMAIN
% The system trees. These are the trees that are shared by all the users.
SYSTEXMF = $TEXMF
% 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
% varfonts feature was enabled in MT_FEATURES in mktex.cnf.
VARTEXFONTS = /var/spool/texmf
% Where to look for ls-R files. There need not be an ls-R in the
% directories in this path, but if there is one, Kpathsea will use it.
%
% Remove $VARTEXFONTS from TEXMFDBS if the VARTEXFONTS directory is below
% one of the TEXMF directories (avoids overlapping ls-R files).
TEXMFDBS = $TEXMF;$VARTEXFONTS
% It may be convenient to define TEXMF like this:
% TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN,$HOME}
% which allows users to set up entire texmf trees, and tells TeX to
% look in places like ~/tex and ~/bibtex. If you do this, define TEXMFDBS
% like this:
% TEXMFDBS = $HOMETEXMF;$TEXMFLOCAL;$TEXMFMAIN;$VARTEXFONTS
% 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
% 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
% files that may be created as well as the formats. For example
% VARTEXMF = /var/lib/texmf
% is used on many Linux systems. In this case, set VARTEXFONTS like this
% VARTEXFONTS = $VARTEXMF/fonts
% and do not mention it in TEXMFDBS (but _do_ mention VARTEXMF).
Reply to: