On Thu, Sep 27, 2007 at 11:11:06PM +0200, Martijn Faassen wrote:
> On 9/27/07, Brian Sutherland <[EMAIL PROTECTED]> wrote:
> > There is one I thought of, but it's a bit backwards.
> > Essentially, Debian has a repository of mostly unmodified original egg
> > tarballs. And, they've already done the hard work of maintaining sane
> > dependencies.
> > So, why not simply re-name the .orig.tar.gz in a Debian release
> > repository to their original names and you have a working set
> > corresponding to that release.
> > If you add your selected personal working set, then you have a basis for
> > working without bleeding.
> Does it contain the Zope 3.4 eggs?
But then my point wasn't that you would use it for Zope3 eggs, but for
everything else. There's a lot of eggs, even in etch. And in lenny there
will be even more. There are few pre-release/alpha/beta versions of
eggs. In fact, a lot of maintainers prefer to release older/stabler
versions than the latest release. And the only changes that happen to
releases are security updates.
Think of it as a stable base upon which to build.
> Will it have Zope 3.5 eggs when we
> need them?
As above, not the point.
> I think if we're going to manage our own gated community,
> it'll be something we need to do ourselves. I just see the need for 1
> per release of piece of software (grok 0.10, grok 0.11, etc), and only
> a vague idea how frameworks would work (I want to use the Foo gated
> community which also uses the Grok gated community) so I must be
> missing something.
Now, how would you use the Grok gated community with the sqlalchemy
gated community if they had common dependencies, and those dependencies
were at different versions in the two communities?
Of course, you could make one _very_ large gated community and "freeze"
it as a release every now and then. Er, basically the same as what
distros are doing, hopefully making their life much easier;)
> Zope3-dev mailing list
> Unsub: http://mail.zope.org/mailman/options/zope3-dev/jinty%40web.de
Zope3-dev mailing list