1deb-triggers(5) dpkg suite deb-triggers(5)
2
6 deb-triggers - package triggers
7
9 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.
27 All triggers in which a package is interested must be listed
28 using this directive in the triggers control file.
29 The “await” variants put the triggering package in
31 triggers-awaited state depending on how the trigger was
32 activated. The “noawait” variant does not put the triggering
33 packages in triggers-awaited state, even if the triggering
34 package declared an “await” activation (either with an
35 activate-await or activate directive, or by using the
36 dpkg-trigger --no-await command-line option). The “noawait”
37 variant should be used when the functionality provided by the
38 trigger is not crucial.
39 activate trigger-name
41 activate-await trigger-name
42 activate-noawait trigger-name
43 Arranges that changes to this package's state will activate the
45 specified trigger. The trigger will be activated at the start of
46 the following operations: unpack, configure, remove (including
47 for the benefit of a conflicting package), purge and
48 deconfigure.
49 The “await” variants only put the triggering package in
51 triggers-awaited state if the interest directive is also
52 “await”. The “noawait” variant never puts the triggering
53 packages in triggers-awaited state. The “noawait” variant
54 should be used when the functionality provided by the trigger is
55 not crucial.
56 If this package disappears during the unpacking of another
58 package the trigger will be activated when the disappearance is
59 noted towards the end of the unpack. Trigger processing, and
60 transition from triggers-awaited to installed, does not cause
61 activations. In the case of unpack, triggers mentioned in both
62 the old and new versions of the package will be activated.
63 Unknown directives are an error which will prevent installation of the
65 package.
66 The “-noawait” variants should always be favored when possible since
68 triggering packages are not put in triggers-awaited state and can thus
69 be immediately configured without requiring the processing of the
70 trigger. If the triggering packages are dependencies of other upgraded
71 packages, it will avoid an early trigger processing run and make it
72 possible to run the trigger only once as one of the last steps of the
73 upgrade.
74 The “-noawait” variants are supported since dpkg 1.16.1, and will lead
76 to errors if used with an older dpkg.
77 The “-await” alias variants are supported since dpkg 1.17.21, and will
79 lead to errors if used with an older dpkg.
80 When a package provides an interest-noawait directive, any activation
82 will set the triggering package into “noawait” mode, regardless of the
83 awaiting mode requested by the activation (either “await” or
84 “noawait”). When a package provides an interest or interest-await
85 directive, any activation will set the triggering package into “await”
86 or “noawait“ depending on how it was activated.
87
89 dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.
901.19.7 2019-06-03 deb-triggers(5)