[Grok-dev] Re: About "Placing your Grok project under version control"

Luciano Ramalho luciano at ramalho.org
Thu May 29 12:56:57 EDT 2008

On Thu, May 29, 2008 at 1:15 PM, Martijn Faassen <faassen at startifact.com> wrote:
> There are a number of extra drawbacks besides the SVN dependency:
> * it's in a subdirectory. I've seen people be tempted to try: "cd bootstrap"
> to run the script, meaning it'll set up a buildout environment in the
> bootstrap subdirectory.
> * these externals typically depend on the buildout trunk. It's possible that
> the buildout trunk introduces incompatible changes to bootstrap.py, causing
> possible breakage. This is something to be avoided
> * it's simply different from placing 'bootstrap.py' in the buildout
> directory itself, meaning that people can encounter two varieties when they
> try out things (the buildout/bootstrap.py and the
> buildout/bootstrap/bootstrap.py variety)
> All these are not terribly bad, but it makes me lean in the direction
> putting in bootstrap.py in the buildout dir itself.
> Note that the new grokproject will do this by default, if I understand
> things correctly. Another argument not to mention more options.

If avoiding the svn:externals is simpler and works better, then it's
the Grok way!



More information about the Grok-dev mailing list