On Thu, 18 Jul 2013, Charles Plessy wrote: > Le Thu, Jul 18, 2013 at 08:55:20AM +0900, Charles Plessy a écrit : > > > > regarding “noawait” triggers, the patch already contains the following, > > which > > is new and improved compared to the existing documentation. > > > > The <tt>*-noawait</tt> directives should be used unless the > > packages awaiting triggers can not satisfy <tt>Depends</tt> > > relationships until the triggers have been processed. > > By the way, are the “noawait” triggers guaranteed to be executed only after > the > triggering package has entered the "Installed" state, or can they be executed > at the same time of other triggers as well ?
There's no such guaranty. A package that triggers another package only knows that the triggers will be processed at some point in the future. It doesn't know if if will before or after its own configuration (the "noawait" doesn't change anything here except that the trigger requirement is not recorded). Even with traditional triggers, it's possible that dpkg will configure a package before processing the triggers that it awaits. What this means is just that the end status will be "Triggers-Awaited" instead "Installed". Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
