Thomas Bushnell BSG <[EMAIL PROTECTED]> wrote:

> However, the preinst in question is no longer in the package.  I'm not
> sure if this is a mistake or not.  I am loath to muck with it at this
> point in the release cycle.

Of course, such a change should not be made in an upload targetted at
etch.  

> If the preinst needs to get back in the package, then the Pre-Depends
> should stay.

I don't know whether a preinst script is needed for other reasons, but
mktexlsr doesn't make sense in a preinst, and the same is true for other
TeX-registering commands.  So using them in postinst (as is currently
done) and lowering the dependency from Pre-Depends to Depends is safe
(post-etch). 

> It's kpsewhich that was needed in the preinst, btw.

If the TeX-related code int he preinst script was similar to the current
postinst script, then the main tool that is called is mktexlsr.
kpsewhich is only used before that in order to get the path argument for
mktexlsr. 

Anyway, you might want to consider to use dh_installtex instead; it
safes you the hazzle of following changes in the TeX setup and just does
the right thing.  It's not in debhelper proper, but in tex-common, but
it follows debhelper conventions.

Regards, Frank
-- 
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)

Reply via email to