Guillem Jover wrote... > Control: severity -1 serious
Why?
> Actually, besides creating triggers cycles, this seems rather an abuse
> of triggers. Because what the package seems to want is to be notified
> when any package is unpacked. This is really not what triggers where
> intended for, even if they "allow" this kind of usage.
There was no indication for me at all you consider this abuse. Of
couse I'm willing to switch to an alternate mechanism if it provides
the goal.
> If you need to hook into dpkg whenever something gets unpacked/configured
> etc, please just switch to use invoke hooks instead (please check the man
> page for further details).
There's surpringly little documentation around about invoke hooks. So
as far as I can see you suggest to drop a sniplet in
/etc/dpkg/dpkg.cfg.d/ that defines a post-commit to invoke (via a
helper script) "/var/lib/dpkg/info/debian-security-support.postinst
configure", or does quite the same on its own. (Just in case, debconf
is used which might result in additional hazzle.)
This sounds a bit weird. And creates a problem: Even if I check
$DPKG_HOOK_ACTION for "configure", this hook will be called for each
package if more than just one is being installed. This will increase
load on my side unless there's a way to to detect the *last*
"configure" invocation of a dpkg run in a sane way - that's the job
the trigger served very well.
Please confirm this approach or suggest a better one.
> In addition as a side comment (but maybe I should file another bug
> instead), please use «dpkg-query -f '${Version}' -W dpkg» instead of
> using «dpkg --version», which is more future proof.
Thanks for the hint, already taken care of.
Christoph
signature.asc
Description: Digital signature
