-----BEGIN PGP SIGNED MESSAGE-----
Stephan Richter wrote:
> On Monday 02 March 2009, Chris Withers wrote:
>> Adam GROSZER wrote:
>>> Someone releases a new package version and your project just break the
>>> next day. That's a nightmare.
>> That shouldn't happen with individual package releases where releases
>> are done sensibly.
> Let me tell you from experience: Before the KGS we had exactely this problem.
> No carefully crafted release can male up for that. And if a single package
> pins versions generically, then you stall development. We also had that
> ha[[en before the KGS came around. Both reasons actually promted my to do the
> KGS in the first place.
> In general, and not specific to you Chris, I think that unless you have
> managed a large set of packages, you should shut up and listen.
Stephan, I *have* managed a large set, and I'm *certain* that the KGS is
useful for many cases: it just doesn't work for me for any large
production application: I don't want to rely on the iffy availability
of eggs from PyPI, for instance, which means that running a separate,
per-project index is my only recourse anyway. Once you are running your
own index, it's contents *are* a KGS, just not one managed using the
That said, I do appreciate the work you have done and are doing to make
the KGS useful for others.
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 -