Chris McDonough wrote:
> This just seems like a blindingly obvious antigoal to actually breaking apart
> the software into more discrete bits using eggs. Why not just stick with a
> tarball release or one single egg if it all has to be versioned through time
> 99% of its consumers as one giant collection of software treated as a unit?
* Repoze and others couldn't use the bits they care about.
* Grok (or anything else) couldn't diverge from a common KGS when it
* individual apps couldn't diverge from a common KGS when *they* need to.
* A clear set of explicit, layered dependencies in software is generally
a good thing. We can start thinking about smaller pieces better. By
splitting up into individually packaged and released bits, we are forced
to think about these things more.
I don't see this as at all incompatible with a group managing a list of
versions that is known to work together, as a service to various groups
which do need such lists anyway.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -