[Resolvconf-devel] The trigger in your Debian packages
jdthood at gmail.com
Sat Jun 4 11:10:20 UTC 2011
Hi, this concerns the resolvconf package.
Resolvconf uses a trigger to delay enabling updates of /etc/resolv.conf
until after the configure phase, thus reducing multiple update runs to
a single run.
Resolvconf triggers itself. The trigger is only used internally, not by
Resolvconf postinst activates the trigger using dpkg-trigger. The package
includes a debian/triggers file that declares interest in the trigger.
> 1/ If your package uses the "interest" directive in the triggers files,
> is it important that the "triggering" packages that activate your triggers
> be considered as not configured (and thus not satisfying dependencies)
> until the trigger has been processed?
Because nothing Depends on resolvconf, it doesn't matter whether or not
resolvconf satisfies dependencies after postinst configure, or later,
after postinst triggered.
> 2/ If your package uses the "activate" directive, is it important that
> your package be considered as not configured (and thus not satisfying
> dependencies) until the trigger has been processed?
Resolvconf doesn't use the "activate" directive. Instead it uses the
So no objection here to the change in default behavior.
More information about the Resolvconf-devel