Hi On Mon, 19 May 2008 12:49:11 +0200 Josselin Mouette <[EMAIL PROTECTED]> wrote:
> As the python-support maintainer, I could recommend it because it has
> more features, like namespace packages (allowing to split modules coming
> from the same directory in non-interdependent packages), Python-Depends
> (allowing to express Provides: in a way that doesn’t break when the list
> of supported python versions changes), or triggers support (leading to
> faster upgrades).
>
> As the maintainer of several python-related packages, I have noticed
> recurrent breakage on user systems caused by bugs in python-central, and
> I avoid it for this precise reason.
Sorry to jumping into this debate, but I also tried debhelper 7 and
because of no current support for pycentral, it meant to switch to
pysupport. I have no strong preference any of them, in fact I have no
idea why I started to use pycentral over pysupport.
What surprised me is different handling of XB-Python-Version field. I
have XS-Python-Version: current and python-central makes
XB-Python-Version: current from this, what I feel is correct (package
is pure Python, no dependency on Python version) and package Depends:
python, what corresponds to this.
However python-support makes XB-Python-Version: 2.5 out of this while
still depending on any python version. Is this bug, I'm doing something
wrong or it is expected behavior? It is just strange to see disparity
between dependencies and Python-Version field.
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
signature.asc
Description: PGP signature
