how to correctly keep version information

Martin Geisler mg at lazybytes.net
Thu Jul 9 07:30:52 CDT 2009


"rupert.thurner" <rupert.thurner at gmail.com> writes:

> hi,
>
> we have multiple branches for versions. an update is done lets say in
> the branch prod, and then gets merged into the default branch.
>
> but there is one properties file contianing the version number. how do
> you best handle such version information so it does not get merged
> into the default branch? "not merge" property like svn? patch queue?
>
> how does mercurial do that mercurial --version prints the correct
> version?

We use 'hg id' when setup.py is run.

You should take a look at the nearest extesion which is designed to help
with this situation:

  http://mercurial.selenic.com/wiki/NearestExtension

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090709/1942e40f/attachment.pgp 


More information about the Mercurial mailing list