[Pkg-zope-developers] Re: Bug#335488: Removal request for old zope packages

[Matthias Klose]

Jeroen van Wolffelaar writes:
> On Sun, Nov 20, 2005 at 09:53:37PM +0100, Fabio Tranchitella wrote:
> > On dom, 20 nov 2005, Jeroen van Wolffelaar wrote:
> > > Why isn't the canonical zope version simply called 'zope' here? If I'd
> > > remove zope, there will be no 'zope' package anymore for people to install.
> > 
> > Well, in my opinion having no 'zope' package is a good thing: zope
> > development is focused on two branches (zope2.x and zope3) so at least two
> > packages will have to coexists. When sarge has been released, zope2.7 was
> > the 'default' zope version, and now it could probably removed in favour of
> > zope2.8, but there are *a lot* of differences between them (read: the Five
> > framework).
> 
> Oh, so there are currently no less than *four* versions of zope in
> unstable?

calm down.

> I'd very strongly suggest to make that zope2 and zope3 only, while there
> surely can be a lot of difference between minor versions, I do not think
> it's a good thing to have multiple minor versions in the archive
> simultaneously, especially considering zope2 is apparantly obsolete
> already.

that's rubbish, not an argument. plone doesn't work with zope3.

> In case there's a security issue in etch, then all of them need
> to be fixed after all, so it saves you as maintainers also some effort.
> 
> As with the name, ok, I see.
>  
> > Another point is that often there is no upgrade path between zope major
> > releases (between 2.7 and 2.8, for example), and having separated packages
> > could be handy in these situations.
> > 
> > So, as zope maintainer and *user* I really would prefer to not have a 
> > 'zope' package but rather install a zopeX one, where X is the release I 
> > want to use.
> > 
> > > So, in short, I'd really really prefer to have just one single zope
> > > version in Debian, rather than multiple.
> > 
> > I think this would be a bad thing for zope users and developers.
> 
> But max two then? Only some really big packages have more than two
> versions, and even there it's typically too much (kernel, python, ...).

it should be a goal to have one 2.x and one 3.x version in etch. if
2.x can be avoided, that's ok.

> > > That are separate things, and I'd like to have those orphaned bugreports
> > > reassigned to ftp.debian.org so I can deal with them.
> > 
> > I'll reassign them to ftp.debian.org.
> 
> Thank's a lot!

yeah, thanks a lot for your constructive comments!

  Matthias