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

[Derrick Hudson]

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.

I used to have some sample code, but I can't find it now.  At any
rate, see http://www.zope.org/Wikis/ZODB/FrontPage/guide/zodb.html for
an introduction to the ZODB API.  It's really quite simple to use.

| 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 kind of agree.

The upstream organization is that ZODB is released as an entity by
itself with its own version number.  During development of zope, a
given version of ZODB is decided upon and imported into the zope
development tree and included in the zope tarball.  The problem that
separating it out in the packaging is that upstream (and thus the rest
of the world) only tests/exercises a single zodb version with a given
zodb version.  I think this would result in extra work keeping the two
packages in sync.  I don't think the gain is very significant, versus
having a single zodb package for use outside of zope and letting zope
use its own copy.  It is also possible, sometimes, for a given zope
copy of zodb to be different than the standalone zodb of the "same"
version.  This is due to limitations in current process and tools used
and is not supposed to happen.  However, it could result in the debian
zope package exhibiting bugs not found in the upstream release.  At
any rate, if someone else wants to put effort into implementing this
proposal, I won't try to stop them.

As far as how to separate it, I think just removing src/ZODB from the
zope tarball and then ensuring the right zodb is in sys.path at
runtime is all that is needed.

-D

-- 
If we claim we have not sinned, we make Him out to be a liar and His
Word has no place in our lives.
        I John 1:10
 
www: http://dman13.dyndns.org/~dman/            jabber: dman at dman13.dyndns.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-zope-developers/attachments/20050810/44b588d6/attachment.pgp