Bug#253094: teTeX's scripts use hardcoded paths for tempfiles (was: Bug#253094: more TMPDIR problems)

[Frank Küster <frank@debian.org>]

clone 253094 -1
retitle -1 tetex-bin's tools use hardcoded TMPDIR variable
forwarded -1 Thomas Esser <te@dbs.uni-hannover.de>
thanks

Hi Thomas,

Riku Voipio <riku.voipio@iki.fi> wrote:

> Hi,
>
> I also noticed that /tmp is hardcoded into many of tetex-bin tools,
> and TMPDIR/TMP is not used very consistenty. See the following command:
>
>  dpkg -L tetex-bin|xargs grep /tmp

The problem with this is that under some circumstances a local admin
might want to change the temporary directory. This can usually be done
by setting the TMPDIR variable. Some of your scripts respect it,
e.g. from texconfig:

tmpdir=${TMPDIR-/tmp}/texconf$$

But others don't. I got, from 
dlocate -L tetex-bin|xargs egrep '/tmp|TMPDIR=' 2>/dev/null | grep -v ^Binary

texmf.cnf          : % TEXMFOUTPUT = /tmp (don't know whether this can be
                                     changed, and it's commented)
/usr/bin/allcm     : cd /tmp
/usr/bin/allec     : cd /tmp
/usr/bin/dvipdft   : TMP=/tmp/dvipdft.$$
/usr/bin/rubibtex  : TEMP=/tmp
/usr/bin/t1mapper  : $logname="/tmp/$logname";
/usr/bin/texdoctk  : my $TempDir = "/tmp"; (this might be a false positive)
/var/lib/texmf/web2c/mktex.opt:  TEMPDIR="/tmp/mt$$.tmp" 
                         (sourced by lots of scripts!)

xdvizilla has been fixed from 2.0.2 to the current beta.

Thomas, are you aware of this? For which of those scripts do you feel
responsible, for which should we contact upstream directly?

Regards, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie