Re: RFC: Proposed updates to the Python Policy to reflect current practices
On Fri, Dec 11, 2009, Emilio Pozuelo Monfort wrote:
> Looks fine to me, but 3.1 needs to be updated too since it currently says that a
> package that needs `foo' must depend on `python-foo', which may not be correct
> anymore with this patch.
Ack
--
Loïc Minier
>From ef9d6552930015aec0a9cb5a0b3d6bb5d2870f96 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lo=C3=AFc=20Minier?= <lool@dooz.org>
Date: Fri, 11 Dec 2009 11:00:24 +0100
Subject: [PATCH 28/30] Require the python- prefix for public modules
Require the python- prefix for packages shipping public modules used by
other packages, and recommend using python-foo for public modules in
general but allow for package shipping multiple modules; thanks Luca
Falavigna and Emilio Pozuelo Monfort.
---
debian/python-policy.sgml | 27 ++++++++++++++++++---------
1 files changed, 18 insertions(+), 9 deletions(-)
diff --git a/debian/python-policy.sgml b/debian/python-policy.sgml
index c49957d..d9cf0dd 100644
--- a/debian/python-policy.sgml
+++ b/debian/python-policy.sgml
@@ -387,14 +387,21 @@
<sect id="package_names">
<heading>Module Package Names</heading>
<p>
- Public modules should have a binary package named
- <package>python-<var>foo</var></package>,
- where <var>foo</var> is the name of the module. Such a
- package should support the current Debian Python version,
- and more if possible (there are several tools to help
- implement this, see <ref id="packaging_tools">). For
- example, if Python 2.3, 2.4, and 2.5 are supported, the
- Python command
+ Public modules used by other packages must have their binary
+ package name prefixed with <var>python-</var>. It is recommended
+ to use this prefix for all packages with public modules as they be
+ used by other packages in the future.
+
+ The binary package for module foo should preferably be named
+ <package>python-<var>foo</var></package>, if the module name
+ allows, but this is not required if the binary package ships
+ multiple modules. In the latter case the maintainer choses the
+ name of the module which represents the package the most.
+
+ Such a package should support the current Debian Python version,
+ and more if possible (there are several tools to help implement
+ this, see <ref id="packaging_tools">). For example, if Python 2.3,
+ 2.4, and 2.5 are supported, the Python command
<example>
import foo
</example>
@@ -536,7 +543,9 @@ XB-Python-Version: ${python:Versions}
</p>
<p>
If the program needs the python module <tt>foo</tt>,
- it must depend on <package>python-foo</package>.
+ it must depend on the real package providing this module, usually
+ <package>python-foo</package> but this name might vary when the
+ package ships multiple modules.
</p>
<sect1 id="current_version_progs">
--
1.6.5
Reply to: