Bug#170969: tetex-bin: Cannot create new fonts

[Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp>]

From: Atsuhito Kohda <kohda@pm.tokushima-u.ac.jp>
Subject: Bug#170969: tetex-bin: Cannot create new fonts
Date: Thu, 28 Nov 2002 17:45:24 +0900 (JST)

> Well, I'm not sure but the following lines in postinst
> of tetex-base;
> 
>      $TEXCONFIG_P font options appendonlydir varfonts
>      $TEXCONFIG_P font vardir /var/cache/fonts
> 
> which are commented out at present should be uncommented ?

Ah, I overlooked postinst of tetex-bin.  The directories will 
be handled with the followings (line #103);

if [ -n "$vardir" ] && ! grep -q "^$vardir\$" $VARFONTSFILE; then
  # A new directory we don't recognise
  echo "$vardir" >> $VARFONTSFILE
  test -d "$vardir" ||
    { mkdir "$vardir" && chmod 755 "$vardir"; }
  test -d "$vardir/pk" ||
    { mkdir "$vardir/pk" && chmod 1777 "$vardir/pk"; }
  test -d "$vardir/tfm" ||
    { mkdir "$vardir/tfm" && chmod 1777 "$vardir/tfm"; }
  test -d "$vardir/source" ||
    { mkdir "$vardir/source" && chmod 1777 "$vardir/source"; }
fi

but $vardir was defined through (line #88)

vardir=`kpsewhich --expand-var='$VARTEXFONTS'`

and this was done before postinst run mktexlsr so I guess
it would be set to /var/spool/texmf and so /var/cache/fonts/pk
etc. were not created.

So it might be needed to run mktexlsr just before the above
definition of vardir too, I think.

Am I right ?

Best regards,			2002/12/2

-- 
 Debian Developer & Debian JP Developer - much more I18N of Debian
 Atsuhito Kohda <kohda@debian.org>
 Department of Math., Tokushima Univ.