Re: Python packages in incoming
Quoting Matthias Klose <doko@cs.tu-berlin.de>:
> Jérôme Marant writes:
> > What about proposal and policy from Neil and his efforts?
>
> - the proposed packaging scheme doesn't allow smooth upgrades between
> one python version and a next version. compare python-1.5 to libc5
> and python-2.1 to libc6. there was a clear upgrade procedure to do
> the transition. The proposed packaging scheme doesn't allow such an
> upgrade. From my point of view, this is a showstopper.
I don't see how this was such a showstopper. Getting the dependancies right to
ensure a clean transition would have been fairly easy.
> - Module paths and installation of arch independant packages should
> be integrated in the current packages.
> Neil's policy proposal addresses this in 1.2 and 2.2.
>
> This should be extended as outlined in
>
> http://lists.debian.org/debian-python/2001/debian-python-200110/msg00017.html
If I recall correctly, Neil's last post was that he was preparing some test
packages that did adopt these extensions. I would be very surprised if the
transition to this scheme was not addressed by Neil.
The biggest hassle with transition would be all the packages that just depend
on python and install themselves into /usr/lib/python1.5. Until all of these
packages have been upgraded, the default python (whether provided by a python
(1.5.2-xxx) wrapper package, a python1.5 package, or a high priority
alternative) has to be 1.5.
--
ABO: finger abo@minkirri.apana.org.au for more information.
Reply to: