Bug#599944: [PATCH] Add a reminder of Pre-Depends policy to §7.2 "Binary Dependencies"
Section 3.5 says:
You should not specify a Pre-Depends entry for a package before this
has been discussed on the debian-devel mailing list and a consensus
about doing that has been reached.
Add a reminder of this to section 7.2, where the semantics of
Pre-Depends are discussed in more detail.
Requested-by: Mattias Ellert <mattias.ellert@fysast.uu.se>
Fixes: http://bugs.debian.org/599944
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
Mattias Ellert wrote:
> I therefore suggest that the paragraph about Pre-Depends in section 7.2
> is amended with a cross-reference to the rule in section 3.5 about the
> requirement about establishing a consensus on debian-devel.
Something like this? Please feel free to improve on it.
policy.sgml | 9 ++++++++-
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/policy.sgml b/policy.sgml
index 6e04c81..1684f78 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -1090,7 +1090,7 @@
</sect>
- <sect>
+ <sect id="dependencies">
<heading>Dependencies</heading>
<p>
@@ -4774,6 +4774,13 @@ Build-Depends: foo [linux-any], bar [any-i386], baz [!linux-any]
package. It is best to avoid this situation if
possible.
</p>
+
+ <p>
+ You should not specify a <tt>Pre-Depends</tt> entry for a
+ package before this has been discussed on the
+ <tt>debian-devel</tt> mailing list and a consensus about
+ doing that has been reached.
+ See <ref id="dependencies">.
</item>
</taglist>
</p>
--
1.7.4.1
Reply to: