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

Re: Bug#231235: arabtex font installation is broken



Florent Rougon <f.rougon@free.fr> schrieb:

> Would probably work, but the real question is: is this (maintainer
> scripts that call updmap & Co) all guaranteed to work when tetex-base is
> unpacked but not configured? If not, one should depend on tetex-base.

I had a look at tetex-base's postinst. This is what it does:

1. Create $LOCALTEXMF, remove old one, these should not be needed by any
   package 

2. Handle updmap - updmap.cfg transition, in detail:

   - remove /etc/updmap if debconf question was answered accordingly 
   - copy the default updmap.cfg from /usr/share/tetex-base/updmap.cfg
     to /var/lib/texmf/web2c/updmap.cfg

   Because this is to be generated when update-updmap is called, I do
   not think this is needed.

3. language.dat handling - this I want to take out. And as far as I can
   see, this is only needed for the creation of format files, and has no
   relation to updmap.

4. Check whether /usr/bin/texconfig and fmtutil.cnf exist and texmf.cnf
   handles the /usr/share/texmf tree, if yes, create format files. This
   is needed if tetex-base is upgraded without tetex-bin being changed,
   and has no relation to updmap.

5. Make links from /etc/texmf/dvips/{psfonts,pdftex,dvipdfm}.map to the
   respective files. 

   If I understood correctly, these are also the output files of
   updmap. Thus these configuration actions are not needed to run
   updmap, but the files generated by updmap will be overridden if it is
   a fresh install of tetex-base (>=2 ?). But if it is a fresh install,
   tetex-bin will also be not configured yet.

   Therefore, calling updmap before tetex-base is configured will work,
   the effect will be overridden by tetex-base's postinst, but restored
   when tetex-bin is configured after tetex-base and calls updmap
   again. 

6. Handle some doc stuff (transition of LOCALTEXMF).

It seems, calling updmap with tetex-{base,bin} being unpacked, but
unconfigured is safe. At least with respect to tetex-base, I didn't
investigate tetex-bin in detail.

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



Reply to: