| 2009-10-01 15:53:17 |
Adomas Paltanavičius |
description |
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.
I think the behavior should be to let 'develop' always override what's in the versions list. If you're going to put packages in the 'develop' list,
you do this explicitly anyway, so there's little risk of mistakes. You want to develop those packages, not use already released versions. |
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.
I think the behavior should be to let 'develop' always override what's in the versions list. If you're going to put packages in the 'develop' list,
you do this explicitly anyway, so there's little risk of mistakes. You want to develop those packages, not use already released versions.
|
|
