Previously Martijn Faassen wrote:
> Stephan Richter wrote:
> > There is a compromise I am willing to take. If package zope.bar depends on
> > a
> > *new feature* or *feature change* in zope.foo 1.3.x, then it should specify
> > the version. In other words specifying open restrictions on the major
> > version
> > levels is okay, but never on the bug fix level. (I just hope this does not
> > bite us later. ;-)
> Yes, I was thinking in this direction too. I can see this as more of an
> issue with bug fixes than with feature changes. This means that
> requirements can only say zope.foo >= x.y, and never zope.foo >= x.y.z.
> What do people think?
If I install a package I want to have a guarantee all aspects of that
package work correctly. With this compromise that is not possible.
Wichert Akkerman <wich...@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -