version tag set by CMAKE is less fancy than the automake setting

[Alpar Juttner]

Using the automake build environment the version tag is something like 503.24b3f18ed9e2, where 24b3f18ed9e2 is the hash id and 503 is a number that is strictly increasing if a version is a descendant of another. This version tag is generated by scripts/chg-len.py.

On the other hand, CMAKE simply sets the hash id as a version string.

[Akos Ladanyi]

Patch attached.

[Alpar Juttner]

Attachment bba484e8f742.patch​ implements a hopefully more portable way of execution of scripts/chg-len.py

It is still pretty cumbersome to get it properly worked. It needs

• a python interpreter in the exec path
• the mercurial modules accessible by this interpreter

Note that TortoiseHg? does not install them, at least it not at the python interpreter's module search path. And TortoiseHg? does not ship a callable python interpreter (to my surprise).

Please check the patch, and also whether or not there is any more user friendly approach to set the version tag.

[Akos Ladanyi]

Replying to alpar:

Attachment bba484e8f742.patch​ implements a hopefully more portable way of execution of scripts/chg-len.py

You changes look fine.

It is still pretty cumbersome to get it properly worked. It needs

• a python interpreter in the exec path
• the mercurial modules accessible by this interpreter

Note that TortoiseHg? does not install them, at least it not at the python interpreter's module search path. And TortoiseHg? does not ship a callable python interpreter (to my surprise).

I couldn't get even this working. I tried installing Mercurial first with the installer of TortoiseHg, then with its own installer. Then tried both Python 2.7 and then 2.6.6. In all cases I added C:\Program Files\Mercurial\library.zip to PYTHONPATH, but chg-len.py kept complaining about missing modules. How did you get the Mercurial Python modules working?

[Alpar Juttner]

Replying to ladanyi:

I couldn't get even this working. [...] How did you get the Mercurial Python modules working?

• Install Python (e.g. ​http://www.python.org/ftp/python/2.7/python-2.7.msi is fine). It will be installed C:\Python27 by default.
• Add C:\Python27 to the system path.
• Get mercurial source code from ​http://mercurial.selenic.com/release/mercurial-1.6.3.tar.gz
• Unpack it somehow... :)
• Open a Visual Studio Command Prompt (I tried VS2008)
• cd mercurial-1.6.3
• python setup.py build
• python setup.py install

After this, scripts/chg-len.py should work properly. (Could you please confirm?)

It is possible to build Mercurial without VS (trough mingw), but it is more cumbersome, see ​http://mercurial.selenic.com/wiki/BuildingOnWindows.

[Akos Ladanyi]

Replying to alpar:

After this, scripts/chg-len.py should work properly. (Could you please confirm?)

Yes, it works for me too now.

Replying to alpar:

Please check the patch, and also whether or not there is any more user friendly approach to set the version tag.

I don't see a better way.

[Alpar Juttner]

This issue has been solved in the main brach by [e74b5db4f2c6] and [7d166b8b8018].