The eggification of Zope 3 in debian

[Brian Sutherland]

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.

The packages are:

python-zope.interface
python-zope.deprecation
python-zope.exceptions
python-zope.testing

Which can be downloaded from my repository at:

deb-src http://lentejasverdes.ath.cx/packages experimental main

These packages necessarily conflict against the current zope3 packages,
but a smooth migration path could be worked out.

You can test the packages by installing python-zope.testing and running
the tests of an installed package using a script [1]. The
python-zope.testing tests themselves fail for reasons I havn't
investigated.

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.

Of course, if there is no discussion, I'll do what I think is best.

If you got this far, thanks for listening.

[1] Testing script is attached, to test python-zope.deprecation run: 
        $ ./test-packages.py -s zope.deprecation

-- 
Brian Sutherland

Metropolis - "it's the first movie with a robot. And she's a woman.
              And she's EVIL!!"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test-packages.py
Type: text/x-python
Size: 1658 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-zope-developers/attachments/20061027/494cb355/test-packages.py