Previously Philipp von Weitershausen wrote:
> On 25 Sep 2007, at 13:20 , Jim Fulton wrote:
> >On Sep 25, 2007, at 3:40 AM, Philipp von Weitershausen wrote:
> >>Charlie Clark wrote:
> >>>Am 25.09.2007 um 02:05 schrieb Tres Seaver:
> >>>>I'd like to break the remaining CMF packages out (moving from '/
> >>>>CMF' to
> >>>>'Products.CMFCore', 'Products.CMFDefault', etc.) and push the
> >>>>2.1.0 eggs
> >>>>out, as well as equivalent changes for PluggableAuthService and
> >>>>Any objections, or other thoughts?
> >>>While I am very sceptical about the move to eggs (I know it's
> >>>inevitable) and I hope we can avoid some of the problems that
> >>>seem to be affecting Grok as a result.
> >>Grok's problems are primarily related to the lack of a working set
> >>definition for Zope 3.
> >I don't know what you mean by this.
> There are several problems.
> * We've had to nail some of the versions because buildout was being a
> bit over-zealous when getting eggs on Windows. It would take the
> newest egg, despite the fact that other eggs had binary releases. I
> guess that's not its fault. But it's a working set problem.
> * When package A depends on Y and package B also depends on Y, but
> with some version restrictions, buidout will first try to get the
> newest version of Y when installing A. But then when installing B, it
> is likely that it has to get a different version of Y. The result is
> a version conflict. This could also easily be fixed with a working
> set that dictates which versions would be used from the beginning.
This is a real problem and something that has to be fixed. It will bite
us with the separate repositories Tres mentioned as well. You need to
be able to analyze the dependency/conflict graph before doing anything
or you will risk breaking a working system.
Wichert Akkerman <[EMAIL PROTECTED]> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests