The eggification of Zope 3 in debian

[Brian Sutherland]

On Mon, Nov 06, 2006 at 09:03:33AM +0100, Fabio Tranchitella wrote:
> * 2006-10-27 01:47, Brian Sutherland wrote:
> > Hi,
> > 
> > I've been thinking quite a bit about how the eggification of Zope 3 is
> > going to affect the packaging of Zope 3. Eggification is a process
> > whereby the current monolithic tarball release is going to be broken up
> > into a large number of smaller tarballs each distributed as an egg.
> > 
> > I've come to the simple conclusion that each zope.* egg should, as far
> > as possible, be treated exactly like a normal python package without any
> > special zope rules. Knowing that code speaks louder than e-mails, I
> > packaged four of the Zope 3 eggs.
> > 
> > [...]
> >
> > I am hoping to start a little bit of a discussion on whether this is the
> > correct direction and if I should commit these to the pkg-zope
> > repository.

Yeah, in the end I committed them to help an off-list discussion.

> Hi Brian, thanks for starting this discussion.

And thanks for responding:)

> I agree with you, we'll need a debian package for every zope.* egg, but I
> hope that we won't have so many source package. For me (speaking as one of the
> zope3 maintainers) having too many source packages could be problematic when a
> new upstream version is released, so I would go with a single source for
> zope3 with a lot of single binaries. This monolithic source tarball could be
> created by us if upstream doesn't provide one.

Ok, so you agree with me that multiple binary packages are the way to
go, but want to put everything into a huge source package to reduce
maintenance costs. A very valid point.

Upstream will also have a maintainence issue managing many packages, and
is looking to automate the management of all these packages using
zc.buildout. My original plan was to try and automate the creation of
many small source packages for a zope release built on top of the
buildout automation.

Though the automation could also be useful for updating a single large
source package.

> We'll obviously need a zope3 meta-package to bring togheter all these binary
> packages and to install the /usr/lib/zope3 stuff, and we have to carefully
> test the upgrade path.

Yeah, I still need to figure out what is the /usr/lib/zope3 stuff.

but +100 for careful testing.

> I know that you follow the zope3 development more closely than myself, do you
> have an ETA for the next release? Do you think it would be possible to start
> working on the eggification with a recent svn checkout?

I don't have an ETA (also, historically, zope misses it's release
date;). But it looks like the zope people are still sorting this out, so
we need to wait a long time before starting any serious work.

-- 
Brian Sutherland

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