[Grok-dev] Re: mars.* vs. grokcore.view, five.grok and releases
Philipp von Weitershausen
philipp at weitershausen.de
Sun Aug 3 11:43:45 EDT 2008
Martin Aspeli wrote:
> Martin Aspeli wrote:
>>> five.grok OTOH still needs lot of love. I tried fixing it up as I
>>> refactored the various grokcore.* packages, but lately I've been
>>> struggling with the fake-eggs thing. Perhaps you can give it a go and
>>> see where the problem is?
>> I am going to have a go later today (in an hour or two) so yeah, I
>> will, especially if you can tell me what is not working.
>> I can probably help with fake-eggs as well if you need that.
> I just checked in a fix to buildout.cfg in five.grok that make the tests
> run. They all still pass. I had to force upgrade zope.component to 3.4
> since it seems something is depending on a 'hook' option that it doesn't
> have with fake eggs and Zope 2.10.6. :-/
> I'm not quite sure this is necessary, but at least the tests pass now.
Cool, thanks! I wasn't aware of the skip-fake-eggs option. I was looking
for an option like that, but plone.recipe.zope2instance's PyPI page
doesn't mention any support for fake eggs at all.
I saw you brought back buildout:eggs. Why? I see this a lot in Plone
buildouts and I always wonder what it's for. AFAIK buildout:eggs isn't
an official option supported by zc.buildout. Frankly, I find it
confusing because it looks like it does something, but so far I couldn't
figure out what it does.
I'm particularly puzzled that you included grokcore.security and
grokcore.view in that option. Why? THey should just be picked up as
dependencies of five.grok.
More information about the Grok-dev