[Resolvconf-devel] resolvconf-event

Thomas Hood jdthood at gmail.com
Wed May 18 13:28:38 UTC 2011

Edward Allcutt <edward at allcutt.me.uk> wrote:
> Is there any particular reason a dpkg trigger is preferred over
> eg. trigger scripts in /etc/resolvconf/install-trigger.d alongside
> the existing update{-libc}.d provisions? I can't see an obvious
> reason why the resolvconf postinst hitting those after resolvconf
> is configured wouldn't guarantee the same behaviour.

That way would have been considered if someone had made
the suggestion earlier, e.g., in response to
http://lists.debian.org/debian-devel/2011/04/msg00719.html.  ;)

One advantage of the dpkg-trigger solution is that the dpkg
trigger response code is in the postinst which often already
contains some resolvconf-related code.  Less code duplication?

But it might still be worthwhile implementing triggering the
way you suggest, if only because then we could then run all
the trigger-response code at "postinst configure" time.  Now
it runs at "postinst triggered" time.  But resolvconf itself
enables updates at "postinst triggered" time, so if other
packages respond to the resolvconf-event trigger after
resolvconf itself does then the result is multiple update
runs.  That's sub-optimal.

> Either way there is still a problem with previous manual configuration[2].

Yes, although that is a different issue.  (I don't think you were
implying otherwise.)

> The schemes still require manually editing /etc/resolvconf/resolv.conf.d/base
> in some cases.

The debconf-controlled scheme implemented by resolvconf involves linking
the original resolv.conf file in as /etc/resolvconf/resolv.conf.d/tail.

The correct way to do static configuration is usually manually to edit


More information about the Resolvconf-devel mailing list