[Pkg-zope-developers] Re: Bug#158554: Separate ZODB package status?

Brian Sutherland jinty at web.de
Wed Aug 10 22:25:39 UTC 2005

On Wed, Aug 10, 2005 at 08:41:01PM +0200, Fabio Tranchitella wrote:
> Il giorno mer, 10/08/2005 alle 20.28 +0200, martin f krafft ha scritto:
> > also sprach Derrick Hudson <dman at dman13.dyndns.org> [2005.08.10.2009 +0200]:
> > > FYI they already do:  http://www.zope.org/Products/ZODB3.4
> > 
> > Cool! I wonder whether we couldn't modularise the Zope package with
> > that. What do pkg-zope people think? Any chance to make upstream do
> > that?
> Really cool, I've just downloaded the tarball and I'll start hacking it
> this night. I'm curious about how zodb works and how I could use it as a
> standalone product.
> Why do you think modularize zope packages using different ZoDB is a good
> idea? In my opinion it would produce a lot of problems about
> compatibilities between zope servers and stand-alone ZoDB packages.
> I don't want to see zodb-3.3.x, zodb-3.4.0 and zodb-3.4.1 packages only
> because zope 2.7.x, 2.8.0 and zope 2.8.1 depends on different zodb
> backend.
> I think one zodb package would be enough.

I was thinking about the simplest way to do this, my first idea would be
to split the zope3-lib package into zope3-lib and zodb-lib. zope3-lib
already puts zodb on the python path so the changes would be quite
minimal and we would avoid any version incompatibilities beween zodb and
zope3 automatically.

Probably there is some really silly and obvious reason why this would
not work though...

Brian Sutherland

Metropolis - "it's the first movie with a robot. And she's a woman.
              And she's EVIL!!"

More information about the Pkg-zope-developers mailing list