[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: (2nd try) Final draft of Python Policy (hopefully ;-)



Matthias Klose <doko@cs.tu-berlin.de> writes:

> It let's a package depend on:
> 
>    python (>= 2.1), python (<< 2.2), python-foo
> 
> and can expect a working default Python version, which has support for
> python-foo.

You mean

    python, python-foo

I presume?

> My proposal would be to build 1.5 and 2.0 packages from one source
> and 2.1 and 2.2 packages from another source package, so the first
> source package and binary packages can easily be removed.

Why is this easier or better than uploading a new version of the
source package that just builds 2.1 and 2.2 packages?

        Joel

-- 
Joel Rosdahl <joel@debian.org>   (PGP and GPG keys available)



Reply to: