On Nov 20, 2007, at 6:34 AM, Martijn Faassen wrote:
> Public bug reported:
>
> When you fix versions using 'versions' in the [buildout] section,
> and you also place the same package in the develop section,
> the version indicated in the versions section is preferred. This
> means that you need to *remove* the version from the
> versions list first in order to change a package into a develop
> package, otherwise the released version will continue to be picked
> up. This makes
> life harder than it should be if you work with long published lists
> of versions. In order to develop packages, you'd need to copy this
> long list and remove those packages that you'd want to change.
No.
Simply override the version for the package you're interested in by
adding:
[versions]
foo =
assuming that your versions section is versions and the package you
want to not have a version for is foo.
On Nov 20, 2007, at 6:34 AM, Martijn Faassen wrote:
> Public bug reported:
>
> When you fix versions using 'versions' in the [buildout] section,
> and you also place the same package in the develop section,
> the version indicated in the versions section is preferred. This
> means that you need to *remove* the version from the
> versions list first in order to change a package into a develop
> package, otherwise the released version will continue to be picked
> up. This makes
> life harder than it should be if you work with long published lists
> of versions. In order to develop packages, you'd need to copy this
> long list and remove those packages that you'd want to change.
No.
Simply override the version for the package you're interested in by
adding:
[versions]
foo =
assuming that your versions section is versions and the package you
want to not have a version for is foo.
Jim
--
Jim Fulton
Zope Corporation