Am Mittwoch, den 24.06.2009, 08:52 -0400 schrieb Chris Rossi:
> Not really missing, just done in a different way. The index itself is
> populated only with a KGS and maintained to be up to date. The
> Agendaless guys also typically make a private index for each customer
> project that they work on--so they still keep the versions pinned, they
> just don't rely on buildout to do that, opting for custom indexes
Well, this approach might be one way to go, but without offering a
version.cfg with all versions used in the release its the only way to go.
I prefer to have the choice.
> As far as using buildout, since bfg is distributed as a bunch of eggs,
> all you really have to do is instruct your buildout to pull from an
> index with the bfg eggs available and then install bfg, so there's not
> much to it, really. If your project only depends on other stuff that
> can be easy_installed there may not be much advantage to using
> buildout, but it's certainly very easy to do and might help to manage
> more complicated deployments.
As said, having two index= in one buildout - the only way to make it work
with eggs from pypi and version pinned repoze.bfg - is a complicated
construct. It works but for sure buildout was not made to support it.
A simple solution to give people a choice is:
a) provide a version.cfg for each release
b) (optional) release everything on pypi as well
Jens W. Klein - Klein & Partner KEG - BlueDynamics Alliance
Repoze-dev mailing list