deb-triggers(5)

1deb-triggers(5)                   dpkg suite                   deb-triggers(5)
2
3
4

NAME

6       deb-triggers - package triggers
7

SYNOPSIS

9       triggers
10

DESCRIPTION

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
16       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
20       The trigger control directives currently supported are:
21
22       interest trigger-name
23       interest-await trigger-name
24       interest-noawait trigger-name
25
26              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. The “noawait”
29              variant does not put the triggering packages in triggers-awaited
30              state.  This  should  be used when the functionality provided by
31              the trigger is not crucial.
32
33       activate trigger-name
34       activate-await trigger-name
35       activate-noawait trigger-name
36
37              Arranges that changes to this package's state will activate  the
38              specified trigger. The trigger will be activated at the start of
39              the following operations: unpack, configure,  remove  (including
40              for   the   benefit   of   a  conflicting  package),  purge  and
41              deconfigure.  The “noawait” variant does not put the  triggering
42              packages in triggers-awaited state. This should be used when the
43              functionality provided by the trigger is not crucial.
44
45              If this package  disappears  during  the  unpacking  of  another
46              package  the trigger will be activated when the disappearance is
47              noted towards the end of the  unpack.  Trigger  processing,  and
48              transition  from  triggers-awaited  to installed, does not cause
49              activations.  In the case of unpack, triggers mentioned in  both
50              the old and new versions of the package will be activated.
51
52       Unknown  directives are an error which will prevent installation of the
53       package.
54
55       The “-noawait” variants should always be favored  when  possible  since
56       triggering  packages are not put in triggers-awaited state and can thus
57       be immediately configured  without  requiring  the  processing  of  the
58       trigger.  If the triggering packages are dependencies of other upgraded
59       packages, it will avoid an early trigger processing  run  and  make  it
60       possible  to  run the trigger only once as one of the last steps of the
61       upgrade.
62
63       The “-noawait” variants are only supported since dpkg 1.16.1, and  will
64       lead  to  errors  if used with an older dpkg. It is thus recommended to
65       add a “Pre-Depends: dpkg (>= 1.16.1)” to any package that wish  to  use
66       those directives.
67
68       The  “-await” alias variants are only supported since dpkg 1.17.21, and
69       will lead to errors if used with an older dpkg. It is thus  recommended
70       to  add  a “Pre-Depends: dpkg (>= 1.17.21)” to any package that wish to
71       use those directives.
72

NAME

SYNOPSIS

DESCRIPTION

SEE ALSO