From: Zooko O'Whielacronx Date: Tue, 8 Jan 2008 17:51:01 +0000 (-0700) Subject: setup: update in-line doc of get-version.py X-Git-Tag: allmydata-tahoe-0.7.0~18 X-Git-Url: https://git.rkrishnan.org/listings/pb3user.py?a=commitdiff_plain;h=1ab03fe9d2c43153db0f99855f9b5fe1d5584098;p=tahoe-lafs%2Ftahoe-lafs.git setup: update in-line doc of get-version.py --- diff --git a/misc/get-version.py b/misc/get-version.py index 39c81c82..f5810676 100644 --- a/misc/get-version.py +++ b/misc/get-version.py @@ -2,11 +2,11 @@ """Determine the version number of the current tree. -This should be run *after* make-version.py . It will emit a single line of -text to stdout, either of the form '0.2.0' if this is a release tree (i.e. no -patches have been added since the last release tag), or '0.2.0-34' (if 34 -patches have been added since the last release tag). If the tree does not -have a well-formed version number, this will emit 'unknown'. +This should be run after 'setup.py darcsver'. It will emit a single line of text +to stdout, either of the form '0.2.0' if this is a release tree (i.e. no patches +have been added since the last release tag), or '0.2.0-34' (if 34 patches have +been added since the last release tag). If the tree does not have a well-formed +version number, this will emit 'unknown'. The version string thus calculated should exactly match the version string determined by setup.py (when it creates eggs and source tarballs) and also