deb-triggers man page on DragonFly

Man page or keyword search:  
man Server   44335 pages
apropos Keyword Search (all sections)
Output format
DragonFly logo
[printable version]

deb-triggers(5)			dpkg utilities		       deb-triggers(5)

NAME
       deb-triggers - package triggers

SYNOPSIS
       triggers

DESCRIPTION
       A  package  declares its relationship to some trigger(s) by including a
       triggers file in its control archive (i.e. DEBIAN/triggers during pack‐
       age creation).

       This  file  contains  directives,  one  per  line. Leading and trailing
       whitespace and everything after	the  first  #  on  any	line  will  be
       trimmed, and empty lines will be ignored.

       The trigger control directives currently supported are:

	    interest trigger-name
	    interest-await trigger-name
	    interest-noawait trigger-name

	    Specifies that the package is interested in the named trigger. All
	    triggers in which a package is interested  must  be	 listed	 using
	    this directive in the triggers control file. The “noawait” variant
	    does not put the triggering packages  in  triggers-awaited	state.
	    This should be used when the functionality provided by the trigger
	    is not crucial.

	    activate trigger-name
	    activate-await trigger-name
	    activate-noawait trigger-name

	    Arranges that changes to this package's state  will	 activate  the
	    specified  trigger.	 The trigger will be activated at the start of
	    the following operations: unpack, configure, remove (including for
	    the benefit of a conflicting package), purge and deconfigure.  The
	    “noawait” variant does not put the triggering  packages  in	 trig‐
	    gers-awaited  state.  This	should	be used when the functionality
	    provided by the trigger is not crucial.

	    If this package disappears during the unpacking of another package
	    the	 trigger  will	be  activated  when the disappearance is noted
	    towards the end of the unpack. Trigger processing, and  transition
	    from  triggers-awaited  to	installed, does not cause activations.
	    In the case of unpack, triggers mentioned in both the old and  new
	    versions of the package will be activated.

       Unknown	directives are an error which will prevent installation of the
       package.

       The “-noawait” variants should always be favored	 when  possible	 since
       triggering  packages are not put in triggers-awaited state and can thus
       be immediately configured without requiring the processing of the trig‐
       ger.   If  the  triggering  packages are dependencies of other upgraded
       packages, it will avoid an early trigger processing  run	 and  make  it
       possible	 to  run the trigger only once as one of the last steps of the
       upgrade.

       The “-noawait” variants are only supported since dpkg 1.16.1, and  will
       lead  to	 errors	 if used with an older dpkg. It is thus recommended to
       add a “Pre-Depends: dpkg (>= 1.16.1)” to any package that wish  to  use
       those directives.

       The  “-await” alias variants are only supported since dpkg 1.17.21, and
       will lead to errors if used with an older dpkg. It is thus  recommended
       to  add	a “Pre-Depends: dpkg (>= 1.17.21)” to any package that wish to
       use those directives.

SEE ALSO
       dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.

Debian Project			  2014-10-15		       deb-triggers(5)
[top]

List of man pages available for DragonFly

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net