Helmut Grohne wrote:
> It gets even worse. Consider the case where a maintainer removes a
> catalog from an existing package and stops calling dh_installcatalogs.
> Then the root catalog would contain a dangling reference and there
> really is no way to fix this anymore, because our code is never invoked
> again. This probably is precisely the reason for why we currently remove
> and add the catalog. To fix this, we will have to keep removing the
> package catalog from the root catalog in prerm, but remember that we did
> it. In the postinst we will have to add it again, iff we removed it
> before. The big question for me would be: How to transfer this state
> from prerm to postinst?

This is why I originally recommended that the registration process be
converted to use triggers. A file fill of catalogs, and a root catalog
file automatically generated from them (which need not be a config file
in /etc) is a much cleaner approach.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to