-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> Hi there,
> Tres Seaver wrote:
>> 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
>> 'versions.cfg' machinery.
>> That said, I do appreciate the work you have done and are doing to make
>> the KGS useful for others.
> Distinguish KGS the concept (a list of locked down versions as
> suggestions to users of the framework) from KGS the implementation.
> Let's agree on the *concept* of a locked down list of versions that's
> maintained by the community, or in fact more than one such list.
Acknowledging the idea that we might have more than one removes the
sting for me.
> If people want to diverge in the implementation, fine. Different
> implementations have different advantages during development and deployment.
Yup, or for different "styles" of projects. As a *personal* example:
*every* time I try to short-cut the process of setting up a
project-specific index representing the KGS *for that project,* I end up
getting burned by something. At this point, I don't even think about
skipping the index setup, any more than I would skip setting up a VCS
repository or mailing lists for the project.
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 -