On Sat, 20 Feb 2010, Piotr Ożarowski wrote:
> > current, >= X.X, << X.X
> > then add additional restrictions?
> dh_py* do that... unless you hardcode Python version f.e. in shebang
hm...
$> acshow impressive | grep -e Version -e Depends
Version: 0.10.2r-5
Depends: python (>= 2.4), python-support (>= 0.90.0), python-opengl,
python-pygame, python-imaging, poppler-utils | xpdf-reader, perl
Version: 0.10.2r-4
Depends: python (<< 2.6), python (>= 2.5), python-support (>= 0.90.0),
python-opengl, python-pygame, python-imaging, poppler-utils | xpdf-reader, perl
-4 had 'current' as its XS-Python-Version
looking into dh_python
# Dependencies on current python
$dep_on_python = 1 if $deps;
$strong_dep = 1 if($deps & (PY_MODULE|SO_MODULE));
if ($dep_on_python) {
addsubstvar($package, "python:Depends", $python, ">= $python_version");
if ($strong_dep) {
addsubstvar($package, "python:Depends", $python, "<<
$python_nextversion");
} else {
addsubstvar($package, "python:Depends", $python, "<<
$python_nextmajor");
}
}
so we get both >> and << ...
pysupport... which calls /usr/share/python-support/private/parseversions
if no pyversions with --pycentral to parse XS-P-V:
if elem=="current":
out.append(os.readlink("/usr/bin/python")[6:])
continue
so we are getting strict versioning again...
BUT if I simply abandon X*-Python-Version fields in my case, then
dh_pysupport will correctly place python dependency without any version.
Well, in my case it should actually be >=2.4 so I better have 2.4- ... but in
any case, both dh_py* tools place versioned one in case of using XS*-P-V field
(which I kinda liked more over yet another debian/bleh file if I followed pure
pysupport way).
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
