Re: triggers question
Joey Hess writes ("triggers question"):
> Of course once all packages are updated to drop the update-menus calls,
> the trigger will only run once per dpkg invocation of a menu-providing
> package. So this is temporary. It's also probably fine to run
> update-menus trice for a while. Just wanted to make sure this is
> as-indended, since I don't remember realizing this would happen when I
> read the original triggers documentation.
Yes, this is as intended. It's a consequence of both using a file
trigger and update-menus.
(Also, while I'm here, I note that #438547 is still open. I hope apt
has been updated already; if not it should be done forthwith.)
> BTW, there seems to be a typo in triggers.txt:
> A file trigger is guaranteed to be activated before the file in
> question is modified by dpkg; on the other hand, a file trigger might
> be activated even though no file was actually modified.
> AFAICS, the file trigger runs AFTER the file is modified. It would
> not be very useful to run it before the file was modified!
The trigger is _activated_ before the file is modified but _run_ much
later. An un-activated trigger means that the triggering event has
definitely not happened since the last run. So we activated it first,
then allow the event to happen, and then the trigger remains activated
until it is processed. A bit like an interrupt with delayed IRQ