Re: trigger question for tex-common
Norbert Preining writes ("trigger question for tex-common"):
> Now, our update-* is so intelligent that it does NOT include parts of
> packages which are in the process of being updated (or not being
> installed at all, but conffiles still present). This is necessary
> because a font package might drop a config file into
> /etc/texmf/updmap.d, an admin might change that, then remove (but not purge)
> the package and the conf file is still present, but we must not (!!!)
> include that part in the final config file.
Right.
> Now comes the problem: When I have
> texlive-lang-german -> depends on tex-common
> and I install
> aptitude install texlive-lang-german
> then first all the packages are unpacked,
> then tex-common is configured/triggered
> then all the other deps are configured
> then texlive-lang-german is configured
>
> When tex-common is triggered not all of the packages are ready being
> configured, so most of the files dropped into the relevant directories
> will not be taken into account by the update-* calls in the trigger action
> of tex-common.
Right.
> Yes, that is the problem.
>
> Ideas for solutions:
>
> What about calling
> dpkg-trigger /etc/texmf/language.d
> and
> dpkg-trigger /etc/texmf/updmap.d
> in the postinst off those packages using it? In that case we could drop
> the file trigger completely and depend on the postinst calling dpkg-trigger.
Yes. This is the right solution. You should rename the trigger so
that it is not a file trigger. Eg, in texmf's DEBIAN/triggers
interest texmf-language
interest texmf-updmap
You probably don't want to call dpkg-trigger directly in
texlive-lang-german's postinst.
Presumably texlive-lang-german calls some script from tex-common to do
this final setup ? That is, the final setup which is also read by
update-* ? In which case, update-* should (when run from a package's
postinst) call dpkg-trigger.
Ian.
Reply to: