[Grok-dev] volunteer task: generating a list of grok dependencies

Martijn Faassen faassen at startifact.com
Tue Sep 18 14:47:36 EDT 2007

Hi there,

Here is a task for a volunteer. It involves the writing of a new 
zc.buildout recipe (I think). This is not as hard as it sounds, by the 
way. :)

We need the ability to generate a list of known-working Grok 
dependencies. All of the dependencies, so if Grok depends on X which 
depends on Y, the indirect dependency Y is also a Grok dependency. This 
list we can then use to pin versions down, so that everybody who uses 
Grok 0.x actually uses the same versions of all egs.

Now where do we get this list from? My proposal would be to have it be 
generated inside of Grok's buildout, by adding a section to its 
buildout.cfg using a special recipe. Buildout already has the ability to 
determine the list of dependencies for our zopectl script (and other 
Python scripts, like the test runner). It bakes these dependencies into 
them. Hopefully it is not too hard a task to create another recipe that 
simply writes this list to a text file.

This text file should have the format so that we can use it inside of 
buildout.cfg using the buildout 'versions' facility. That's something like:

egg-name = 3.4.1



More information about the Grok-dev mailing list