From: Zooko O'Whielacronx <zooko@zooko.com>
Date: Tue, 11 Mar 2008 02:26:02 +0000 (-0700)
Subject: setup: generate a unique revision number for each build
X-Git-Tag: allmydata-tahoe-0.9.0~37
X-Git-Url: https://git.rkrishnan.org/maximilian?a=commitdiff_plain;h=f58acd69b4bcb9723c325319f011ca67abcf9dbd;p=tahoe-lafs%2Ftahoe-lafs.git

setup: generate a unique revision number for each build
---

diff --git a/GNUmakefile b/GNUmakefile
index 73ccc002..627291cd 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -67,7 +67,7 @@ show-eggspath:
 # http://pypi.python.org/pypi/darcsver It is necessary only if you want to
 # automatically produce a new _version.py file from the current darcs history.
 make-version:
-	$(PYTHON) ./setup.py darcsver
+	$(PYTHON) ./setup.py darcsver --count-all-patches
 
 # We want src/allmydata/_version.py to be up-to-date, but it's a fairly
 # expensive operation (about 6 seconds on a just-before-0.7.0 tree, probably
diff --git a/setup.py b/setup.py
index dd0f2ea0..850d55a5 100644
--- a/setup.py
+++ b/setup.py
@@ -104,7 +104,7 @@ setup_requires = []
 # version stamp in src/allmydata/_version.py, with a version number derived from
 # darcs history.
 # http://pypi.python.org/pypi/darcsver
-setup_requires.append('darcsver >= 1.0.0')
+setup_requires.append('darcsver >= 1.1.1')
 
 # setuptools_darcs is required to produce complete distributions (such as with
 # "sdist" or "bdist_egg"), unless there is a PKG-INFO file present which shows