Previously Philipp von Weitershausen wrote: > Proposal > -------- > > I think zc.buildout's version mechanism in buildout.cfg is a good > technical basis. It's simple, light-weight and easy to version-control. > For example, the Grok project could create a grok-0.11.cfg defining the > known working set for the Grok 0.11 release, with the following contents:: > > [grok-0.11] > grok = 0.11 > ZODB = 3.8.0 > zope.component = 3.4.0 > ... > > Then, the Grok folks could distribute this file and everybody who wanted > to use Grok 0.11 would simply have to put the following two lines into > their buildout.cfg:: > > [buildout] > ... > extends = grok-0.11.cfg > versions = grok-0.11 > > With this, it'll be easily possible to switch to a newer version of e.g. > ZODB3 by overriding the setting in buildout.cfg:: > > [buildout] > ... > extends = grok-0.11.cfg > versions = grok-0.11 > > [grok-0.11] > ZODB = 3.9.0 # this overrides whatever is set in grok-0.11.cfg > > > The only problem is that distributing grok-0.11.cfg is a bit tedious. > How about if buildout could get it from the web?
How about making it available from an egg, through a hook in egg-info perhaps? Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com