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

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



Le Sun, Aug 04, 2013 at 09:14:09AM +0900, Charles Plessy a écrit :
> Le Sat, Aug 03, 2013 at 09:41:59AM -0700, Jonathan Nieder a écrit :
> > 
> > If I end up with time to work on it, what I would probably do is to
> > split the patch into smaller changes that can be considered and
> > applied independently, which would hopefully be less intimidating for
> > area experts to review.
> 
> Hi Jonathan,
> 
> I have split the patch in the following parts:
> 
> 	0001-Document-Dpkg-states.patch
> 	0002-Document-postinst-triggered.patch
> 	0003-Document-concepts-syntax-and-control-information-fil.patch
> 	0004-Detail-the-two-trigger-kinds-explicit-and-file.patch
> 	0005-Details-about-Dpkg-states-when-processing-triggers.patch
> 	0006-Document-the-behaviour-of-triggers-when-packages-are.patch

Hi Jonathan and everybody,

how about starting with 0001-Document-Dpkg-states.patch ?  It documents the
Dpkg states without intrusive normative changes.

> >From 5d3279e10152d6ecb8b2b4bf226f7e7a380228e1 Mon Sep 17 00:00:00 2001
> From: Charles Plessy <plessy@debian.org>
> Date: Sun, 4 Aug 2013 07:17:03 +0900
> Subject: [PATCH 1/6] Document Dpkg states.
> 
> ---
>  policy.sgml              | 47 +++++++++++++++++++++++++++++++++++++++++++++++
>  upgrading-checklist.sgml |  4 ++++
>  2 files changed, 51 insertions(+)
> 
> diff --git a/policy.sgml b/policy.sgml
> index cb1093f..e3598f1 100644
> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -3959,6 +3959,53 @@ Checksums-Sha256:
>  	</p>
>  
>  	<p>
> +	  Dpkg defines the following states for the packages.
> +	  <taglist>
> +	    <tag>Not-Installed</tag>
> +	    <item>
> +	      The package is not installed on the system.
> +	    </item>
> +
> +	    <tag>Config-Files</tag>
> +	    <item>
> +	      Only the configuration files of the package exist on the system.
> +	    </item>
> +
> +	    <tag>Half-Installed</tag>
> +	    <item>
> +	      The installation of the package has been started, but not
> +	      completed for some reason.
> +	    </item>
> +
> +	    <tag>Unpacked</tag>
> +	    <item>
> +	      The package is unpacked, but not configured.
> +	    </item>
> +
> +	    <tag>Half-Configured</tag>
> +	    <item>
> +	      The package is unpacked and its configuration or the processing
> +	      of one of its triggers has not yet completed for some reason.
> +	    </item>
> +
> +	    <tag>Triggers-Awaited</tag>
> +	    <item>
> +	      The package awaits trigger processing by another package.
> +	    </item>
> +
> +	    <tag>Triggers-Pending</tag>
> +	    <item>
> +	      The package has been triggered.
> +	    </item>
> +
> +	    <tag>Installed</tag>
> +	    <item>
> +	      The package is unpacked and configured.
> +	    </item>
> +	  </taglist>
> +	</p>
> +
> +	<p>
>  	  Broadly speaking the <prgn>preinst</prgn> is called before
>  	  (a particular version of) a package is unpacked, and the
>  	  <prgn>postinst</prgn> afterwards; the <prgn>prerm</prgn>
> diff --git a/upgrading-checklist.sgml b/upgrading-checklist.sgml
> index 0a111d4..41a1e84 100644
> --- a/upgrading-checklist.sgml
> +++ b/upgrading-checklist.sgml
> @@ -55,6 +55,10 @@ Unreleased.
>    <item>New section documenting the <tt>Package-Type</tt> field in source
>    package control files.
>    </item>
> +<tag>6.1</tag>
> +  <item>The Dpkg states are now documented.  The Policy has been proofread
> +  and occurences of "Failed-Config" have been corrected to "Half-Configured".
> +  </item>
>  <tag>11.5.2</tag>
>    <item>Stop recommending to serve HTML documents from
>    <file>/usr/share/doc/<var>package</var></file>.
> -- 
> 1.8.4.rc0
> 

Have a nice day,

-- 
Charles


Reply to: