ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-04-12 21:32:59 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

setup: generate a unique revision number for each build

Browse Source
This commit is contained in:
Zooko O'Whielacronx 2008-03-10 19:26:02 -07:00
parent 5108a73c6f
commit f58acd69b4
2 changed files with 2 additions and 2 deletions

2
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

2
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