Hi, On Mon, 21 Apr 2008, Helge Kreutzmann wrote: > This can be used by maintainer scripts in complex and conditional > situations where the file triggers, or the declarative B<activate> triggers > control file directive, are insufficiently rich. It can also be used for > testing and by system administrators (but note that the triggers won't > actually > be run by dpkg-trigger)." > > a) What are "conditional situations"?
A test with "if ...; then dpkg-trigger a-trigger-name; fi" for example. > b) What does "declarative" in "declarative B<activate> triggers > control file directive" mean? By installing a triggers control file with an 'activate' directive you "declare" to dpkg that you want to activate a particular trigger whenever the status of the package changes. The trigger activation is "declarative" because it's explicitly listed in the triggers file. It's defined that way by opposition to a direct call to dpkg-trigger in a postinst (which can be executed only in some special situation (cf your point (a))). Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
