Re: (2nd try) Final draft of Python Policy (hopefully ;-)
Joel Rosdahl writes:
> 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?
You may want to do this, if you _know_ that your packages work with
python2.4 and python3 as well.
> > 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?
If you support 2.1 and 2.2 only, yes, then it's easiser :)
Matthias
Reply to: