From f58acd69b4bcb9723c325319f011ca67abcf9dbd Mon Sep 17 00:00:00 2001 From: Zooko O'Whielacronx Date: Mon, 10 Mar 2008 19:26:02 -0700 Subject: [PATCH] setup: generate a unique revision number for each build --- GNUmakefile | 2 +- setup.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) 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 -- 2.45.2