-----BEGIN PGP SIGNED MESSAGE-----
Dieter Maurer wrote:
> Chris Withers wrote at 2009-4-2 20:42 +0100:
>>> KGS the
>>> concept is very easy to implement; you just make available on some URL a
>>> buildout versions.cfg, or you run your own package index.
>> OK, the former I can see happening on an end-user project, the latter is
>> just too much work.
Not really. Collect the tarballs, run a script, configure Apache to
serve that diretory. Probably less than half an hour per release, or
less once the pattern is established, with the upside that builds
against the "controlled" index are not susceptible to the breakage
induced by varying levels of "release discipline" among the hundreds of
folks whose pacakges are on PyPI.
> Tres has earlier proposed a meta egg to represent "versions.cfg" in
> a setuptools only (non buildout) environment.
> A meta egg is an egg that only list dependencies and does not contain
> code of its own.
I also intened that eggified-Zope2 releases would "pin" the underlying
versions, so that installing it would give you a fixed configuration.
Others overrode that choice, preferring to have an "upgradeable"
version, which then requires a KGS. It might be sensible to distribute
both variants, actually.
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -