Re: Bug#231235: arabtex font installation is broken

[frank@kuesterei.ch (Frank Küster)]

Clint Adams <schizo@debian.org> schrieb:

>> If it doesn't work well, this is bad for anyone installing arabtex from
>> unstable on his woody system. But this is tolerable, if Clint doesn't
>> manage (or want) to handle both situations. You should document in
>> README.Debian that the missing dependency on tetex>=2 is only to ensure
>> a smooth upgrade.
>> 
>> Clint, are you still tuned in?
>
> Yes.  So I should either version the tetex-extra dependency to (>=2) or
> unversion the tetex-base dependency and expand the postinst to run
> mktexlsr if update-updmap is unavailable?

If you want to ensure compatibility with tetex-1.x, don't aks me. But
AFAIR, mktexlsr wasn't sufficient to get fonts registered, you needed to
execute /etc/texmf/updmap or something like this.

I am not sure whether a versioned dependency on tetex-extra will do. I
suggest to Depend on tetex-extra, without version, and to Depend on
tetex-base >=2.0 and tetex-bin >=2.0 (because update-updmap and
/usr/sbin/updmap are in tetex-bin, not in tetex-base). As Florent has
shown, this will give a smooth upgrade, even if tetex-base Conflicts
with older arabtex versions. The upgrade will be as follows:

- Because of the Conflicts, arabtex-$newversion will be unpacked first. 

- After this, tetex-base can be unpacked without errors (and tetex-bin
  anyway). 

- In the configure phase, the order in which the postinst scripts are
  executed is: tetex-base, tetex-bin, arabtex, because Depends requires
  that the depended-on package is configured before the depending
  package is configured.

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