On Nov 17, 2007, at 2:18 PM, Jim Fulton wrote:

I'm trying to get ZODB4, ZopeX3 and Zope X3.

Nice.

One of the failures is Zope. This is not meant to be installed as an egg. AFAIK, not everything in PyPI is necessarily a package distribution. If I'm mistaken, we should probably remove it, otherwise, you might want to explicitly remove it from your check.

I'll add it to the exclude list, as it looks like its meant just to be a "promotional" page. OTOH, it might be a good idea to create a meta- egg that represented Zope-3-the-appserver and upload it into this distribution, maybe with a console script that created an instance?

The output included a failure for the spread module. I think your gcc error filter isn't working. :)

Yeah, I don't have one of those, but I just added an exclusion for SpreadModule. - C

I think if we can fix zope.i18n's dependencies, some dependency chains will get reduced. - C On Nov 17, 2007, at 5:22 PM, Philipp von Weitershausen wrote:

Chris McDonough wrote:

...

Attempting to easy_install all 'zope'-related releases using the script at http://svn.repoze.org/playground/trunk/chris/zopesvnchecker/releasechecker.p... , the results were: 8 failures, 183 successes. See http://www.plope.com/static/misc/rcresults-2007-11.17.txt for details.

Thanks for these results.

The recurring number of 77 dependencies is suspicious. No doubt the various zope.app packages with their huge amount of dependencies are behind this. Apparently, those 77 eggs are the minimal Zope3 installation we can do from eggs.

This demonstrates very well that we could just as well have kept large parts of zope.app (the ones that are among those 77 eggs) in one big egg and made our lives a lot easier.