[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#582109: debian-policy: document triggers where appropriate

Le Sun, Feb 24, 2013 at 04:41:55PM +0900, Charles Plessy a écrit :
> I am having a look at how to document triggers.  In order to simplify the
> explanation and re-use more easily material from the file above, I think
> that we would benefit from documenting the dpkg states for a package.

How about adding the following to the Policy's section 6.1 (Introduction to
package maintainer scripts) ?

          Dpkg defines the folowing states for the packages.
              The package is not installed or has been purged.

              The package has been removed; its configuration files remain.

              Errors happened during installation, upgrade or removal.  Solving
              them requires the package to be re-installed.

              The files contained in the package have been successfuly unpacked, 
               but the maintainer scripts have not been executed.  Thus, the 
               files created by the maintainer scripts are not yet available.

              The package has been unpacked, and an error occured during the
              execution of one of its maintainer scripts.

              The package has been unpacked and configured, and its
              installation activated some <prgn>dpkg</prgn> triggers that have
              not yet been executed.

              Some triggers handled by this package have been activated and are
              not yet executed.

              The package is installed, no further action is required.

For the half-installed and half-configured, I am not very confident on what I
wrote and surely feedback.

Have a nice week-end,


Reply to: