[Grok-dev] Re: grokproject, grok tarball and the i18n part

[Maurits van Rees]

Maurits van Rees, on 2008-05-06:
> There are workarounds:
>
> - Calling "bin/buildout install eggbasket" before doing a complete
>   buildout.  grokproject should be able to do that easily enough; and
>   for end-users this could be documented.

I added this call to my grokproject branch.

> - Mess around with bootstrap.py to run that install step immediately.

I added this to that branch as well.  Hm, this now means that the
eggbasket recipe gets called twice, but the second time is an upgrade,
at which point it does not actually do anything.


Let's look at the time it takes to get a grokproject up and running
now on my desktop computer.

On trunk the bootstrap takes less than 3 seconds; an install takes 2
minutes 25 seconds.

On the maurits-using-eggbasket branch bootstrapping takes 1 minute 30
seconds; installing takes 17 seconds.

So on the branch it takes less time.  And of course it delivers on the
intended goal that a new grokproject should not need several servers
to be up and running.

I think it should be safe to merge this branch back to trunk.  Any
objections?


For reference, here are the only eggs that need to get installed after
the eggbasket install is done:

lovely.recipe
z3c.testsetup
zc.recipe.filestorage
zc.recipe.testrunner
zc.zodbrecipes
zc.zope3recipes


BTW, has anyone tried the latest grokproject (trunk or branch) on
Windows?  It would be good to know that it works there as well before
making a release.

Cheers,

-- 
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]