On 12-8-2010 11:23, Alexandre Fayolle wrote:
I'm forwarding the message below (with some slight editing) to the pyro-core
mailing list for feedback.
Irmen, in order to ease parallel installation of pyro3 and pyro4, would you
mind changing the package name of pyro4 from 'pyro' to 'pyro4'? I think this
would be beneficial for many users and that it would ease migration to pyro 4
(by easing the detection of which version is installed, and allowing legacy
application to run side by side with new apps). Being able to have both
versions installed is a must have from a system administration point of view
(both installed on the same machine, and both running on the same LAN).
Alexandre, are you referring to the debian software package name?
I'm not making those packages myself. That is taken care of by the package maintainer
which is now Carl Chenet, I believe.
I added him explicitly to the cc-list.
Carl, can you comment on this? I think Alexandre has a valid concern.
Logilab is a pyro 3 heavy user (with the Cubiweb [1] framework), and we cannot
afford to migrate to pyro 4 right now.
Thanks for your feedback.
[1] http://www.cubicweb.org/
Regards
Irmen de Jong
---------- Forwarded Message ----------
Subject: [Python-modules-team] please provide 2 packages: pyro and pyro4
Date: Thursday 12 August 2010, 10:55:56
From: Alexandre Fayolle<[email protected]>
To: [email protected]
CC: [email protected]
As Sylvain said, pyro4 changes the ABI and therefore this update breaks any
application deployed on the system depending on pyro 3.x.
The best move imo would be to keep pyro4 in Debian experimental, since most
users are using the official stable release (3.x branch), and to revert to pyro3
in sid/testing.
I suggest providing 2 packages pyro and pyro4, which could at first conflict
with each other. I think upstream should be contacted, and asked to change the
namespace of pyro 4.x to pyro4 in order to ease parallel installation of both
versions.
In any case, please do not release squeeze with pyro 4.x as "pyro". This will
be very painful. We really want pyro 3.9 in squeeze, as 4.x will break
external applications.
I'll be happy to help on this matter once
_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
