[Grok-dev] Re: grokproject: version pinning in setup.py
faassen at startifact.com
Thu Jul 3 14:55:04 EDT 2008
I'd like to make sure that when the buildout runs (for the first time or
thereafter) the version of zc.buildout and the version of any recipes we
used are pinned down, somehow. Suggestions on how to do this would be
welcome. Given the bugs we've had in zc.buildout releases, I think we've
dodged the bullet for now, but I also think we run a concrete risk.
The problem with zc.buildout is the bootstrapping issue; how do we
constrain the recipe to install an egg if the recipe itself is an egg?
I'm not sure how bad the bootstrapping issues are; if we constrain
recipes, what happens?
As to the actual installation of grokproject itself, we still have a
tricky situation. Something might happen to the dependencies that causes
grokproject to stop working upon installation. Of course we have far
less dependencies, and existing grok installations will continue to
work, but installation by beginners of Grok would still be broken until
someone actually thinks of telling us something is wrong. That's bad enough.
I'd like to avoid this situation, somehow. I'm not sure how to go about
it though, and perhaps the solution is worse than the problem. But I
think it makes sense to think about options here.
More information about the Grok-dev