[Grok-dev] Re: grokproject: eggs-directory in generated buildout.cfg

[Philipp von Weitershausen]

Jan-Jaap Driessen wrote:
> When I start a project using grokproject (v0.6), the 'eggs-directory' in 
> the generated buildout.cfg may not mean anything on the machines of my 
> co-developers nor on the web servers I am deploying my code on.
> 
> How do you cope with this? Would it not make more sense not to have an 
> eggs-directory directive in the generated buildout.cfg?

Indeed. zopeproject is actually smart enough to detect that you've got a 
setting in ~/.buildout/default and won't generate an eggs-directory 
option in case you choose the default eggs location by simply hitting enter.

I should get around backporting this to grokproject, or simply basing 
grokproject on top of zopeproject (in which case I'll have to 
forward-port some things). Help appreciated :)