[Pkg-zope-developers] Re: [zope] Zope packaging policy

[Donovan Baarda]

On Sat, 2004-02-21 at 20:57, Luca - De Whiskey's - De Vitis wrote:
> On Sun, Jan 11, 2004 at 12:57:40PM +0100, martin f krafft wrote:
> [...]
> >   http://people.debian.org/~luca/zope-policy.html
> [...]
> 
> This link is back, and I've placed the draft for the new policy i was writing
> just before i disappeared. I wanted it to be discussed and approved (in some
> way) before zope 2.7 release, but ...
> 
> Comments are welcome.

I've just had a look and have a few comments.

The first and second pages talk about a default "zope" package and hint
at "other zope package versions". The third page then talks about the
zopeZ-pythonX.Y package providing zopeZ packages, and "zope" depending
on a particular "zopeZ". 

Do we really need to support multiple concurrent zope versions? My gut
feeling is yes, especially with the transitions to zope 3 becoming more
and more rocky, it will make sense to have old zope versions available.

Do we need the -pythonX.Y part in the names? It seems Zope versions will
always be tightly bound to particular Python versions. This means the Z
part should make the pythonX.Y part redundant, and we don't need to
support multiple installs of the same Zope version using different
versions of Python.

Has much thought been given to zope-foo packages that support multiple
zopeZ versions?

Also in the past I have had problems with zope-foo packages that
specified a particular version of python2.1, only to become out of date
as zope moved on to python2.2, but still worked (zope-zwiki...). Perhaps
a dependency on zopeZ alone without specifying a particular pythonX.Y
would fix this?

-- 
Donovan Baarda <abo@minkirri.apana.org.au>
http://minkirri.apana.org.au/~abo/