eggs and zope3

[Brian Sutherland]

Hi All,

Lately, I might have had a bit more time to work on zope3 packaging. 

I'd like to start work on packaging the zope 3.4 eggs as separate
packages.

There's one point where we have an issue. Last time I posted to this
list, and talked about packaging all the eggs, the consensus seemed to
be to keep all the eggs in one source package. But I think things have
changed since then. It's become very apparent that the eggs are going to
have different release cycles. That basically makes the "single source
package" idea quite difficult to manage as we'll be re-uploading it all
the time for every minor release. 

I've been finding uscan and uupdate to be quite successful in managing
updates.

Anyway, I'd like to start packaging the dependencies (~100) as packages
like:

python-zope.interface, python-zope.testing 

putting the packaging code in alioth, but the packages in an external
repository (perhaps to be later uploaded to Debian if it works out).

One problem is maintaining the thing working while changing
dependencies. To combat that, I'll be including autopkgtest scripts in
each package that will run the inbuilt tests.

Comments? suggestions? objections?

-- 
Brian Sutherland