On Thu, 2003-09-11 at 02:51, Alexandre Fayolle wrote: > On Wed, Sep 10, 2003 at 01:35:42PM +0200, Andreas Rottmann wrote: > > Alexandre Fayolle <[EMAIL PROTECTED]> writes: [...] > > OK, so keep them around until the version in question is dropped from > > the archive? > > This would be nice. Or until upstream drops support for 2.1. > > If you already support 2.2 and 2.3, then supporting > 2.1 does not require much more work (since you already have to deal with > multiple calls to setup.py, alternatives, etc.), and it is of great > value to people who work with python and have to support legacy > versions.
If the python2.1[-foo] packages were built properly to the policy, there should be no need to build new ones for the archive unless they have bug fixes. The only exception would be binary extension modules that need to be recompiled for libc upgrades. > Now this leaves us with the question: how long should Debian ship > python2.1? I'd be inclined to leave them there until they get nasty bug reports that no one can be bothered fixing... drop them as they break, unless demand insists they get fixed, until demand insists they all go away to free up archive space. -- Donovan Baarda <[EMAIL PROTECTED]> http://minkirri.apana.org.au/~abo/