Re: [PATCH] dpkg: do not activate triggers for unchanged conffiles
Hi!
On Sat, 2009-11-07 at 17:06:09 -0600, Jonathan Nieder wrote:
> Currently, dpkg lets interested packages know when saving a
> backup (.dpkg-dist file) for an updated conffile that is not
> going to used.
>
> This is, strictly speaking, harmless, since file triggers were
> never a guarantee that a file was actually modified. But on one
> hand, the triggered action can be an expensive no-op (such as
> restarting a server process), and on the other hand, any package
> that relies on triggers being activated in this case will break
> once some user decides not to keep a .dpkg-dist file. So it
> seems safer to avoid the unnecessary and misleading trigger.
On that specific case “cfo_keep | cfof_backup”, the user has been
prompted, dpkg stopped, allowing to modify the installed conffile,
through dpkg spawning a shell or backgrounding itself, or through
another external means. So dpkg does not currently have a way to track
if the installed conffile got modified, and that's why the trigger.
For example some times depending on the amount of changes, I either
forward port them from inst → new, or the other way around. In the
latter case you have to keep your current file, and it has been
modified.
regards,
guillem
Reply to: