[Grok-dev] syncing versions.cfg in grokcore.* family

Martijn Faassen faassen at startifact.com
Thu Sep 17 12:27:34 EDT 2009

Reinout van Rees wrote:
> On 2009-09-17, Jan-Wijbrand Kolman <janwijbrand at gmail.com> wrote:
>> Conclusion from the neanderthal II sprint:
>> Packages like the grokcore.* family extend the latest versions listing 
>> on http://grok.zope.org/releaseinfo/grok-*.cfg. These packages can of 
>> course always override and amend this list in their own buildout.cfg.
>> This prevents having to repeat the list over and over again in the 
>> packages with the risk of to much diversion.
> Sounds like an "extends=http://somewhere.else" which prevents you from running
> buildout when you don't have an internet connection?
> Or has this been fixed in recent buildouts?

No, it'll prevent you from running the buildout. We think this is 
important when creating a Grok-based project and when checking out a 
Grok-based project's buildout.

It's not so important for the grokcore.* packages themselves. Ease of 
maintenance is more important there and that's why we want to clearly 
share the same versions lists for all of them.



More information about the Grok-dev mailing list