[Grok-dev] how to manage the versions files, a plan

Vincent Fretin vincent.fretin at gmail.com
Sat Feb 27 06:55:33 EST 2010

Indeed, you can simply use:

extends-cache = versions
extends = http://svn.zope.org/*checkout*/groktoolkit/trunk/grok.cfg

create the versions directory first
then bin/buildout
and you will have 3 files in versions/

The next time you can do
bin/buildout -o


On Sat, Feb 27, 2010 at 10:08 AM, Jan-Wijbrand Kolman
<janwijbrand at gmail.com> wrote:
> Martijn Faassen <faassen at startifact.com> wrote:
>> I'm +1 to a versions-update script that donwloads the new versions.
> A few random thoughts:
> * I like the idea of some support scripts and tool surrounding the release *and*
> to make the grokproject tool a bit more intelligent about retrieving version
> information and putting it into the newly created project.
> However,
> * There's the "extends cache" option in buildout that we could encourage (like
> grokproject encourages to have a ~/.buildout/default.cfg). If this option works
> reliably, we could actually do less than we do now, as all extends reference can
> be left in place as the information is cached for offline use. In other words,
> the newly created project's buildout could "just" extend the grok.cfg and
> ztk.cfg and zopeapp.cfg...
> Just some thoughts :-)
> regards,
> jw
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> https://mail.zope.org/mailman/listinfo/grok-dev

More information about the Grok-dev mailing list