[Pkg-zope-developers] Re: zope-debhelper and zope-common (was: (no subject))

[A Mennucc]

--mvpLiMfbWzRoNl4x
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 09, 2005 at 02:25:01PM +0100, martin f krafft wrote:
> also sprach Andreas Tille <tillea@rki.de> [2005.03.09.1352 +0100]:
> > While I think dropping (teh current!) Zope package is a good idea it wo=
uld
> > be definitely not good for Sarge.  Perhaps we should do the same like P=
ython
> > packages and provide zope2.6, zope2.7 and zopeX.Y while having one zope
> > package which just depends form the *default* zope version.  On the oth=
er
> > hand we should make sure that keeping to many versions of Zope would on=
ly
> > be confusing for our users ...
>=20
> I do not understand why we provided zope2.7 anyway. Why not upgrade
> 2.6 to 2.7? There are not that many differences, are there? Sounds
> to me like 2.7 should have lived in experimental for a while first.
> zope3 will be its own package, that's for sure.

because of different APIs , many things that work with zope2.6
will not work with zope2.7=20

so, if we force users to drop one version wrt to another,
many things will break:
this is unacceptable to people that deploy real web application,
(and bet their money and time and company on that ).
I have friends that work in small companies, that
live on zope-based applications , and I was strongly recommended
to keep multiple versions around.

btw, this is not different than what happens with
tcl/tk 8.0 8.1 8.2 8.3 8.4
python 2.0 2.1 2.2 2.3 2.4
gcc and family
etc etc

there has been a long tradition in Debian that
any critical component may come in different version:
so why not zope ?

a.

--=20
Andrea Mennucc
 "Ukn ow,Ifina llyfixe dmysp acebar.ohwh atthef"

--mvpLiMfbWzRoNl4x
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCMAu69B/tjjP8QKQRAhBQAJ9b2pd2A2x/2xUdvy02UREV+pPNRQCgkez9
cTFt40qFXB097uXC0U+h46I=
=UiIG
-----END PGP SIGNATURE-----

--mvpLiMfbWzRoNl4x--