-debian-policy (3.5.2.1) unstable; urgency=low
+debian-policy (3.5.3.0) unstable; urgency=low
* Removed recommendation on packaging-manual
closes: Bug#86507, #93620, #93705
* Correct bug severities closes: Bug#91276
* Correct typos etc. in policy-process
* Rename all .text files as .txt
+ * Fixed the to to typo in policy. closes: Bug#87007
+ * Changed packaging manual ==> dpkg documentation closes: Bug#88651
+ * [ACCEPTED 14/03/2001] Deprecate confusing closes: Bug#87828
+ Build-Depends arch syntax
+ * [AMENDMENT 29/03/2001] Clarification of example closes: Bug#87711
+ configuration files
- --
+ -- Manoj Srivastava <srivasta@debian.org> Sun, 15 Apr 2001 13:36:19 -0500
debian-policy (3.5.2.0) unstable; urgency=low
-- Julian Gilbey <jdg@debian.org> Thu, 15 Feb 2001 12:13:00 +0000
+debian-policy (3.5.0.1) unstable; urgency=low
+
+ * Richard Braakman and Micheal Dorman have exressed their resignation
+ from policy maintenance duties.
+ * fixed the date thinko in upgrading checklist. Thanks to Sébastien
+ Montagne <sebastien.montagne@netcourrier.com> closes: Bug#84236
+
+ -- Manoj Srivastava <srivasta@debian.org> Sun, 15 Apr 2001 11:24:51 -0500
+
debian-policy (3.5.0.0) unstable; urgency=low
* There have been numerous changes since the last major change, and
that have no editorial powers. At the moment, the list of
maintainers is:
<enumlist>
- <item>
- <p>Michael Alan Dorman <email>mdorman@debian.org</email></p>
- </item>
- <item>
- <p>Philip Hands <email>phil@hands.com</email></p>
- </item>
<item>
<p>Julian Gilbey <email>jdg@debian.org</email></p>
</item>
<p>
This list here is not supposed to be exhaustive. Most fields
are dealt with elsewhere in this document and in the
- packaging manual.
+ dpkg documentation.
</p>
<sect1 id="f-Package"><heading><tt>Package</tt>
</heading>
<var>package</var> (<var>version</var>) <var>distribution(s)</var>; urgency=<var>urgency</var>
* <var>change details</var>
- <var>more change details</var>
+ <var>more change details</var>
* <var>even more change details</var>
-- <var>maintainer name and email address</var> <var>date</var>
is done in brackets after each individual package name and
the optional version specification. The brackets enclose a
list of Debian architecture names separated by whitespace.
- An exclamation mark may be prepended to each name. If the
- current Debian host architecture is not in this list and
- there are no exclamation marks in the list, or it is in the
- list with a prepended exclamation mark, the package name and
- the associated version specification are ignored completely
- for the purposes of defining the relationships.
+ Exclamation marks may be prepended to each of the names.
+ (It is not permitted for some names to be prepended with
+ exclamation marks and others not.) If the current Debian
+ host architecture is not in this list and there are no
+ exclamation marks in the list, or it is in the list with a
+ prepended exclamation mark, the package name and the
+ associated version specification are ignored completely for
+ the purposes of defining the relationships.
</p>
<p>
<footnote>
<p>
It used to do this by calling <prgn>ldd</prgn>, but it
- now calls <prgn>objdump</prgn> to to this. This
+ now calls <prgn>objdump</prgn> to do this. This
requires a couple of changes in the way that packages
are built.
</p>
upgrading <tt>conffile</tt>s.
</p>
</footnote>
+ </p>
- <p>
The other way to do it is via the maintainer scripts.
In this case, the configuration file must not be listed as
a <tt>conffile</tt> and must not be part of the package
have to do any configuration other than that done
(semi-)automatically by the <tt>postinst</tt> script.</p>
- <p>
- A common practice is to create a script called
- <tt><var>package</var>-configure</tt> and have the
- package's <tt>postinst</tt> call it if and only if the
- configuration file does not already exist. In certain
- cases it is useful for there to be an example or template
- file which the maintainer scripts use. Such files should
- be in <tt>/usr/share/doc</tt> if they are examples or
- <tt>/usr/lib</tt> if they are templates, and should be
- perfectly ordinary <prgn>dpkg</prgn>-handled files
- (<em>not</em> <tt>conffiles</tt>).</p>
+ <p>
+ A common practice is to create a script called
+ <tt><var>package</var>-configure</tt> and have the
+ package's <tt>postinst</tt> call it if and only if the
+ configuration file does not already exist. In certain
+ cases it is useful for there to be an example or template
+ file which the maintainer scripts use. Such files should
+ be in <tt>/usr/share/<package></tt> or
+ <tt>/usr/lib/<package></tt> with a symbolic link
+ from <tt>/usr/share/doc/<package>/examples</tt>
+ if they are examples, and should be
+ perfectly ordinary <prgn>dpkg</prgn>-handled files
+ (<em>not</em> <tt>conffiles</tt>).
+ </p>
<p>
These two styles of configuration file handling must
projects / debian / debian-policy.git / commitdiff