deb-conffiles(5) [plan9 man page]

deb-conffiles(5)						    dpkg suite							  deb-conffiles(5)

NAME

       deb-conffiles - package conffiles

SYNOPSIS

       conffiles

DESCRIPTION

       A  package  declares  its  list	of  conffiles  by  including a conffiles file in its control archive (i.e. DEBIAN/conffiles during package
       creation).

       This file contains a list of files, one per line.  They should be listed as absolute pathnames, and should exist  in  the  binary  package,
       otherwise  dpkg(1)  will ignore them (although by default dpkg-deb(1) will refuse to build such binary packages).  Trailing whitespace will
       be trimmed, and empty lines will be ignored.

EXAMPLE

       /etc/alternatives/README
       /etc/cron.daily/dpkg
       /etc/dpkg/dpkg.cfg
       /etc/logrotate.d/dpkg

SEE ALSO

       dpkg-deb(1), dpkg(1).

1.19.0.5							    2018-04-16							  deb-conffiles(5)

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
       package 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

	    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.

	    activate 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.

	    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.

SEE ALSO

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

Debian Project							    2009-03-15							   deb-triggers(5)