Re: More updates for the policy
Hi Andy,
On Mon, 19 Jun 2006, Andreas Barth wrote:
> We shouldn't have two vastly different ways to do it.
Life would be best if we had already taken a decision... we know this but it is
not going to happen until we have more experience with both python-central and
python-support.
> Either, XS-Python-Version is the right thing. Than it should be in
> policy.
>
> Or there is another good mechanismn. Then it shouldn't be in policy.
Policy should document usage. Right now we're starting to use
python-central and python-support and we don't know which approach is
best. So the policy shouldn't favor either approach but rather document
what's common between both approaches.
The common part is quite clear:
- everything in one python-foo
- the dependencies that have to be generated
The new field is not part of the common part. For technical reasons, we
have to find a way to differentiate clearly between new policy and old
policy and for this the best approach suggested is the idea of Pierre
Habouzit, a Standards-Version field dedicated to Python. It's the smallest
common denominator that I have found on which both parties could agree.
> The new dak headers were explicitly mentioned in Mexico, and there was
> more than one reason to add them.
What are those reasons?
I only know two reasons for those headers:
- python-central use them for its internal work
- it may help track a transition and discover which packages need to be
updated
BTW, the syntax of the Python-Version field comes directly from
python-central and it has not been discussed if the current syntax is the
best needed to achieve the second point.
I can easily find out packages which need to be updated for a python
transition by looking for packages with a dependency "python (<< 2.X)".
> If we want to drop them again, we really should discuss
> them here, and speak about the reasons we had in Mexico to accept them.
I welcome discussion as always.
> And, I don't think that "they're no more required" right now - just
> dh_python could live without them. And I really want further discussions
> before jumping to conclusions.
Right, and the dh_python change doesn't forbid maintainer to continue
using XS-Python-Version as it will continue to work without problem.
That's why I'll go forward with the change and we'll have more time for
discussing what we want in the long term.
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
Reply to: