[Grok-dev] Re: How do I install Grokstar?

Martijn Faassen faassen at startifact.com
Mon May 28 16:43:05 EDT 2007


Sebastian Ware wrote:
> I am running on Macosx 10.4.9 with python 2.4 which I have compiled from 
> source, and Zope3.3 which I also compiled from source.
> 
> I have followed the instructions, making sure I use the python 2.4 
> compiler (it failed first time around "Error: Couldn't find a 
> distribution for zc.recipe.zope3instance" because I used python 2.3, but 
> I saw the comments about this in an earlier thread). Eventually 
> [buildout] ends in a massive list that kind of looks like this:
> 
> """
> zope.i18n 3.4dev-r73098 is required by zope.app.testing 3.4.0a1.
> zope.app.testing 3.4.0a1 is required by zope.app.catalog 3.4.0a1.
> zope.app.catalog 3.4.0a1 is required by zc.catalog 1.2dev-r74688.
> zc.catalog 1.2dev-r74688 is required by hurry.query 0.9.2.
> hurry.query 0.9.2 is required by Grokstar 0.0.
> zope.app.testing 3.4.0a1 is required by zope.app.intid 3.4.0a1.
> zope.app.intid 3.4.0a1 is required by zope.app.catalog 3.4.0a1.
> zope.app.catalog 3.4.0a1 is required by zc.catalog 1.2dev-r74688.
> zc.catalog 1.2dev-r74688 is required by hurry.query 0.9.2.
> hurry.query 0.9.2 is required by Grokstar 0.0.
> """
> 
> ...only it repeats itself with small variations over probably 100 lines...

Ugh, part of this is the annoying Zope 3.3/ Zope 3.4 transition problem 
again. Zope 3.3 doesn't use eggs for the core yet, only for extensions. 
Zope 3.4 created lots of extensions for Zope 3 core packages. Grokstar 
includes an egg that used to depend on nothing, but now, in an updated 
version, depends on some Zope 3.4 eggs, which means it starts including 
virtually the entirety of Zope 3.4. This will all become easier once 
we've all transitioned to Zope 3.4, but it's a pain right now.

I don't know though why it starts doing the endless loop. It sounds like 
some dependency conflict that somehow starts looping. This is odd. I can 
look into this again wednesday night with JW and we should check in a 
fix for all these issues then, so we get Grokstar at least in a working 
state again.

Regards,

Martijn



More information about the Grok-dev mailing list