On Fri, May 11, 2007 at 01:08:26PM -0400, Tres Seaver wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Bernd Dorn wrote: > > On 11.05.2007, at 17:29, Chris Withers wrote: > > > >> Fred Drake wrote: > >>> On 5/11/07, Chris Withers <[EMAIL PROTECTED]> wrote: > >>>> I dunno, do we actually need an "offical big zope 3 release" > >>>> anymore? > >>> No. What's more, we don't even want to use one anymore. > >> cool :-) > >> > >> My only slight concern here is when people make changes in one > >> satellite project, they break another one and don't realise. But I > >> guess the buildbot should catch that, right? > > > > i talked with jim about this and we agreed in that specifying > > versions in eggs is not a good idea. The best way imho is to use > > buildout's 'version' section in your application's buildout to nail > > down all eggs to a specific version. > > - -1; a "meta" egg would work fine as a place to specify hard-wired > dependencies. Not every Zope3 user is going to be using buildout. > Note that such a "mega-egg" would likely specify the "transitive > closure" of its dependency graph, as well.
It's just going to get very difficult very quickly to manage such a meta egg with over 100 or so dependencies. Though I guess there'll be automated tools to manage this. I think another alternative is to separate the releases into different "repositories", kinda like "All zope 3.0.0 eggs are at http://download.zope.org/distribution/3.0.0/";. -- Brian Sutherland _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
