[Grok-dev] grok trunk - buildout broken

Martijn Faassen faassen at startifact.com
Tue May 19 15:08:43 EDT 2009


Jan-Wijbrand Kolman wrote:
>> Of course we could just stick with pinning 
>> zope.container, but it's really code that we actually shouldn't have to 
>> worry about at all for the time being.
> Note that it apparently is something related to the tests of 
> grokcore.view - hopefully this means reverting is a) not too difficult 
> and b) does not have too many repercussions for projects already using 
> 1.0a3.

We should on the longer term look at how we can change those tests so 
they won't require containers anymore.

>> We should build a step into our release procedure to point out any 
>> packages that aren't pinned down.
> As been noted earlier in this thread, we can easily let the buildout 
> process report, by way of an extension, any packages that were not 
> specifically pinned down in the versions.cfg.
> I propose using this buildout extension and set the "rule" that 
> everything that gets pulled in, should also be listed in the 
> versions.cfg, preferably based on the the KGS we choose for the grok 
> "line of developement" at that moment. Anything that falls outside of 
> the KGS needs to be discussed on the list. Would that work?

Yes, that rule sounds good. Would it be enforced by the software or 
would someone need to manually check on it? We should in the latter case 
make it part of our release steps.

> I'll try to revert grokcore.view and release it.




More information about the Grok-dev mailing list