[Grok-dev] Re: when "trunk" becomes a distribution point: disaster?
faassen at startifact.com
Fri May 16 13:07:31 EDT 2008
Reinout van Rees wrote:
> There's an older revision of grokproject where there's a simple copy of
> the file both in the skeleton and in grokproject itself. Should be real
> quick to change back.
I'm +1 to doing this. This way a project that you've grokprojected can
be checked out by others who can get going with really simple
instructions, and without the risk of breakage that relying on an
external to the buildout trunk does increase.
If the behavior of bootstrap.py ever significantly changes, I think it's
reasonable for us to add an upgrade note and tell people to use a newer
More information about the Grok-dev