optilude+lists at gmail
May 24, 2009, 9:24 AM
Post #3 of 3
(510 views)
Permalink
|
Maurits van Rees wrote:
> Adam GROSZER, on 2009-05-24:
>> Hello,
>>
>> Following just happened. The project has KGS 3.4 versions as a base,
>> locally I wanted to override lxml to >= 2.1.1.
>>
>> [...snip...]
>> extends = http://download.zope.org/zope3.4/3.4.0/versions.cfg
>> versions = versions
>>
>> [versions]
>> lxml >= 2.1.1
>
> Only assignment (=) is allowed here, not comparison (>=).
Right. And note that it's =, not ==. A [versions] block is not a version
spec, it's an explicit pin.
You may also be interested in the buildout.dumppickedversions, which
helps you analyse what buildout actually picked, and possibly in
http://good-py.appspot.com, which helps you manage version pins in
different "layers" for different platforms. For example, you could add a
second line to 'extends' with another KGS layered on top of the Zope
3.4.0 one, overriding some versions and adding others.
> Comparison is allowed in a few other spots, for example:
>
> recipe = my.recipe.name >= 1.0
And in any 'eggs' line.
Martin
--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book
_______________________________________________
Zope-Dev maillist - Zope-Dev [at] zope
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
|
