[Distutils] Better version pinning in buildout (buildout-versions)

[Marius Gedminas]

On Mon, Jan 07, 2013 at 09:45:58AM -0500, Jim Fulton wrote:
> No.  The versions-file can be used with the existing mechanism.
> I tried, but apparently failed, to make this clear in the proposal.
> 
> If both a versions file and a versions section is used, the versions
> section behaves as it does now and versions in the versions file
> override versions specified in the versions section.

This seems backwards to me.

Consider this example

    $ cat buildout.cfg

      [buildout]
      I-forgot-the-suggested-new-spelling-for-a-versions-file = versions.txt
      parts = ...

      ...

    $ cat mg.cfg

      [buildout]
      extends = buildout.cfg
      versions = versions

      [versions]
      SomePackage = overridden_version

I would expect bin/buildout -c mg.cfg to use my overridden version from
mg.cfg, not the one from versions-file.txt.

Also, having two similar but slightly distinct mechanisms for version
pinning?  I'm -1 on that.

Marius Gedminas
-- 
lg_PC.gigacharset (lg = little green men language, PC = proxima centauri)
	-- Markus Kuhn provides an example of a locale
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130107/84ac4875/attachment.pgp>