1deb-triggers(5) dpkg suite deb-triggers(5)
2
6 deb-triggers - package triggers
7
9 debian/triggers, debian/binary-package.triggers, DEBIAN/triggers
10
12 A package declares its relationship to some trigger(s) by including a
13 triggers file in its control archive (i.e. DEBIAN/triggers during
14 package creation).
15 This file contains directives, one per line. Leading and trailing
17 whitespace and everything after the first # on any line will be
18 trimmed, and empty lines will be ignored.
19 The trigger control directives currently supported are:
21 interest trigger-name
23 interest-await trigger-name
24 interest-noawait trigger-name
25 Specifies that the package is interested in the named trigger. All
26 triggers in which a package is interested must be listed using this
27 directive in the triggers control file.
28 The “await” variants put the triggering package in triggers-awaited
30 state depending on how the trigger was activated. The “noawait”
31 variant does not put the triggering packages in triggers-awaited
32 state, even if the triggering package declared an “await”
33 activation (either with an activate-await or activate directive, or
34 by using the dpkg-trigger --no-await command-line option). The
35 “noawait” variant should be used when the functionality provided by
36 the trigger is not crucial.
37 activate trigger-name
39 activate-await trigger-name
40 activate-noawait trigger-name
41 Arranges that changes to this package's state will activate the
42 specified trigger. The trigger will be activated at the start of
43 the following operations: unpack, configure, remove (including for
44 the benefit of a conflicting package), purge and deconfigure.
45 The “await” variants only put the triggering package in triggers-
47 awaited state if the interest directive is also “await”. The
48 “noawait” variant never puts the triggering packages in triggers-
49 awaited state. The “noawait” variant should be used when the
50 functionality provided by the trigger is not crucial.
51 If this package disappears during the unpacking of another package
53 the trigger will be activated when the disappearance is noted
54 towards the end of the unpack. Trigger processing, and transition
55 from triggers-awaited to installed, does not cause activations. In
56 the case of unpack, triggers mentioned in both the old and new
57 versions of the package will be activated.
58 Unknown directives are an error which will prevent installation of the
60 package.
61 The “-noawait” variants should always be favored when possible since
63 triggering packages are not put in triggers-awaited state and can thus
64 be immediately configured without requiring the processing of the
65 trigger. If the triggering packages are dependencies of other upgraded
66 packages, it will avoid an early trigger processing run and make it
67 possible to run the trigger only once as one of the last steps of the
68 upgrade.
69 The “-noawait” variants are supported since dpkg 1.16.1, and will lead
71 to errors if used with an older dpkg.
72 The “-await” alias variants are supported since dpkg 1.17.21, and will
74 lead to errors if used with an older dpkg.
75 When a package provides an interest-noawait directive, any activation
77 will set the triggering package into “noawait” mode, regardless of the
78 awaiting mode requested by the activation (either “await” or
79 “noawait”). When a package provides an interest or interest-await
80 directive, any activation will set the triggering package into “await”
81 or “noawait“ depending on how it was activated.
82
84 dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg/triggers.txt.gz.
851.21.8 2022-05-25 deb-triggers(5)