Previously Philipp von Weitershausen wrote:
> Proposal
>
>
> I think zc.buildout's version mechanism in buildout.cfg is a good
> technical basis. It's simple, light-weight and easy to version-control.
> For example, the Grok project could create a grok-0.11.cfg defining the
> known wor
Philipp von Weitershausen wrote at 2007-9-3 13:46 +0200:
> ... known working sets ...
>Thoughts?
As you wrote, pinning down versions induces potential conflicts.
Therefore, it might be helpful, if the known working set would not
need to be a singleton (consists of just one element).
Assume the f
Problem
---
We recently had our first Grok release (0.10). Due to various versions
of certain packages, we had to pin down the versions of those packages
to ensure you'd get the version we had tested the release with, and to
prevent buildout from downloading the versions of packages that h
