On Wed, 30 Mar 2011, Goswin von Brederlow wrote: > > Note also that the trigger activation is a no-op if the > > qlustar-image-common is > > not configured which means that you have to regenerate your image in the > > "configure" of qlustar-image-common as well as in the "triggered" case. > > Is a package allowed to trigger itself? Or is that already considered a > cycle?
I don't see how a package can trigger itself. If you run dpkg-trigger from the postinst, the package is not configured yet and the trigger is a no-op. It's the same for a file trigger which is executed during unpack. Cheers, -- Raphaël Hertzog ◈ Debian Developer Follow my Debian News ▶ http://RaphaelHertzog.com (English) ▶ http://RaphaelHertzog.fr (Français) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
