Re: Bug#447231: debian-policy: New Python policy missing
forcemerge 447231 462377
thanks
Manoj Srivastava wrote:
> On Fri, 19 Oct 2007 10:46:53 +0200, Bernd Zeimetz <bernd@bzed.de> said:
>
>> the new Python policy is in use since several months now and should be
>> integrated.
>
> Are these the policies that are currently in use?
>
>> http://wiki.debian.org/DebianPython/NewPolicy
>
> This seems more like a HOWTO document, and relies heavily on
> using debhelper. The language is not what I would expect of a normative
> document; it is fine for what it appears to be, a user guide.
>
> In general, the policy should define interfaces and
> requirements, and leave implementation details to the user; which is
> not the case here.
Right, but at the moment I don't know of any better document which
describes on how to apply the new policy to packages. I think there're a
few things missing on the page, but otherwise it's still uptodate.
>> http://people.debian.org/~srivasta/manoj-policy/
>
> This document is slightly better, but there is no indication
> that this has been accepted by the Debian Python crowd. Has there been
> a ratification of this document by folks who use python?
If I compare the content of the document with the things I see in the
modules/apps team, I didn't find any problems so far, also it documents
rtupdate, which is something I've never seen documented before.
>> are both much more uptodate than
>> http://www.debian.org/doc/packaging-manuals/python-policy/
>
> Umm, I am not sure where that document comes from, but it
> certainly does not seem to be part of the Debian technical policy, so I
> am not sure what the relevance is here.
>
> Perhaps the Python Debian community should come to a consensus,
> update the page on http://www.debian.org/doc/packaging-manuals/, and
> then move to have whatever the result is be added to the
> technical policy?
This would be my preferred way, too - unfortunately the 'Debian Python
maintainer' insists of being the only person who is allowed to change
the 'policy'. He blocks any progress, while most python related packages
(except python itself - unfortunately) are maintained in teams.
Best regards,
Bernd
--
Bernd Zeimetz
<bernd@bzed.de> <http://bzed.de/>
Reply to: