Op 07-01-13 15:42, Jim Fulton schreef:
On Mon, Jan 7, 2013 at 6:12 AM, Maurits van Rees
<m.van.r...@zestsoftware.nl> wrote:
Say there is a buildout config with one or more versions that are not
pinned. What would the effect be of the various options? Here is a truth
table:
allow-p-v update-v-f result
false false buildout quits with error
false true buildout quits with error
No, as described in the proposal, if update-versions-file is true (and
assuming that you've specified a versions-file) then there would not
be an error if allow-picked-versions was false and there were picked
versions, because they'd be added to the versions file and thus
would become un-picked.
But logically, if buildout picks versions and puts them in a version
file, then they are still picked during the current buildout run, so
when allow-picked-versions is false, buildout should quit, independent
of the update-versions-file setting.
I guess I actually simply would not use this particular combination of
settings. If I want buildout to quit with an error when a version is
picked, I should just use false for both settings.
So: no big deal.
--
Maurits van Rees: http://maurits.vanrees.org/
Zest Software: http://zestsoftware.nl
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig
