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

Re: update-updmap vs. updmap --enable



On 29.05.04 Florent Rougon (f.rougon@free.fr) wrote:
> Hilmar Preusse <hille42@web.de> wrote:

Hi,

> > The entry can be disabled using "updmap --disable xyz.map". It
> > will not be deleted from updmap.cfg, but just commented.
> >
> 
> Other than that, if you call "updmap --disable foo.map", you will
> end up with "#! Map foo.map" in updmap.cfg, whereas no cruft will
> be left if you remove map files with the updmap.d scheme.
> 
Thats what I said.

> > but I think "updmap --(en|dis)able" fulfils that requirement.
> > Just for the archive: if we change that -- the affected packages
> > would be: arabtex hlatex thailatex.
> 
> How did you come up with this list?
> 
1. I don't know if that list is still valid. I didn't check recently.
2. See the discussion in #213310 starting Dec 05. The script I've
posted here recently. apt-rdepends gives you a list, which packages
depend on tetex-bin. That scripts greps through post{in,rm} whether a
package calls updmap. It assumes just, that all package authors
provide bug free packages ;-).

H. 
-- 
Paranoia is simply an optimistic outlook on life.
  http://hilmarpreusse.forum-rheinland.de/



Reply to: