[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: plan of next upload

From: Hilmar Preusse <hille42@web.de>
Subject: plan of next upload (was: Re: po-debconf template for tetex-bin)
Date: Wed, 29 Oct 2003 19:12:30 +0100

> > problem of upgrading pxfonts might need a bit more investigation, I
> > guess.
> > 
> Well, we had a thread started on Sep 15 by me about that (Subject was
> "#197870, #197891, #197954").

Yes, I know that thread but I am lazy and didn't follow
them at that time.

>                     My final solution was to ask the question about
> removing /etc/texmf/dvips/updmap in the config-stage, but delay the
> removal at least to the preinst stage. My guess was, that it doesn't
> hurt us if we don't remove that file in the config stage, so we
> should delay it until the prerm-skript of pxfonts has been executed.

I read the thread again and I thought I could got your 
point.  So your solution was;


if [ -f ${etcdir}/updmap ]; then
    db_input high tetex-base/oldupdm || true
    db_go || true


if [ -f ${etcdir}/updmap ]; then
    db_get tetex-base/oldupdm || true
    if [ X"$RET" = X"true" ]; then
        rm -f ${etcdir}/updmap*

(a bit modified but this would be your intention, I guess.)

It seemd simple, clean and reasonable fix.  If anyone
doesn't find a problem I will do this fix in our CVS.

> Further: tetex-doc Recommends tetex-bin. I would as alternative
> recommend dvi2tty. Additionally we need html-viewer, pdf-viewer,
> postscript-viewer. So:
> Recommends: tetex-bin (>> 2.0) | dvitty, pdf-viewer, postscript-viewer, www-browser
> dvi2tty displays dvi-Files on a terminal without needing the whole
> teTeX-stuff. The version in unstable is GPL.
> Sorry, for speaking about that in this thread. I've deleted already
> the other one from my HD.

No problem.  And this idea looks reasonable too.

Regards,			 2003-10-31(Fri)

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

Reply to: