Hey, On 9/27/07, Tres Seaver <[EMAIL PROTECTED]> wrote: [snip] > > I already replied to this, but let me point out why I think such a gated > > community would not be *sufficient* for my purposes. > > > > I want to be able to release package X, and have a way for other people > > to install it and it not break, ever. This can be done with hard version > > numbers in install_requires today, but people object to this reasonably > > as it would reduce flexibility of component reuse. If we want to have a > > way to reproduce installations *exactly* and we want to still allow > > flexibility, a gated community while hopefully increasing the quality of > > individual releases still won't guarantee that package X won't break > > when someone else tries to install it. > > If package 'X' points its 'index_url' to the GC, then anybody trying to > install 'X' will look up / pull dependences from the GC: that setting > takes the Cheeseshop completely out of play.
Does this mean that every Zope 3 application or framework will need to manage their own gated community? That seems totally unacceptable. Regards, Martijn _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com