tahoe-lafs/setup.cfg

[easy_install]
# Tahoe-LAFS actually does work at least as well as any package works when
# zipped, but zipping eggs causes various problems
# (http://bugs.python.org/setuptools/issue33 ), and generally makes it harder
# for people to get at the source code, and doesn't actually provide any
# benefits that I am aware of.
zip_ok=False

# Tahoe-LAFS depends upon several libraries (foolscap, twisted, pycryptopp,
# zfec, and others). Left to its own devices, setuptools will look on PyPI for
# these and will download them at build time. The 'find_links=' entry in
# setup.cfg causes setuptools to look for these dependent tarballs in
# tahoe-deps/ and ../tahoe-deps/ before it resorts to downloading them from
# PyPI.

# http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz contains a
# bundle of these dependencies (as Python source distributions or "sdists"). So
# it you want to avoid the build-time download (say, if you're on an airplane,
# or a desert island), just grab a copy and unpack it in your tahoe darcs tree.

# Alternatively, if you're building from a release/nightly tarball instead of
# a darcs tree, the 'sumo' tarball variant will include all of these
# dependencies in the tahoe-deps/ directory.

find_links=misc/dependencies tahoe-deps ../tahoe-deps
 http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-dep-sdists/
 http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/

# The following is a directory on the test grid which holds a bunch of packages
# of dependencies.  It is commented-out because the test grid has gone away and
# a new one -- the Volunteer Test Grid -- is not yet publicly usable.
# http://testgrid.allmydata.org:3567/uri/URI%3ADIR2-RO%3Asnrfwfxatrci35zdgjnzxxx2ke%3Aunarxv347edtku3xzmefy4mcdmfngxzeb72iyqcadbjzjpczjx5a/index.html

# Other sites that we might want to list:
# http://sourceforge.net/project/showfiles.php?group_id=78018&package_id=79063
# http://pypi.python.org/pypi/pywin32
# (See http://tahoe-lafs.org/trac/tahoe-lafs/ticket/142 .)

[aliases]
build = darcsver --count-all-patches develop --prefix=support make_executable build
test = darcsver --count-all-patches develop --prefix=support make_executable build trial
sdist = darcsver --count-all-patches sdist
install = darcsver --count-all-patches install
bdist_egg = darcsver --count-all-patches bdist_egg
trial = darcsver --count-all-patches trial
sdist_dsc = darcsver --count-all-patches sdist_dsc
test_mac_diskimage = darcsver --count-all-patches test_mac_diskimage
setup: add a setup.cfg file which instructs setuptools to install all eggs in unzipped form and to always copy them into the target directory (even if they are already installed somewhere else on the path that setuptools searches, which includes the CWD) 2008-01-22 13:46:47 -07:00			`[easy_install]`
setup: update comments and URLs in setup.cfg 2010-05-03 23:16:53 -07:00			`# Tahoe-LAFS actually does work at least as well as any package works when`
			`# zipped, but zipping eggs causes various problems`
			`# (http://bugs.python.org/setuptools/issue33 ), and generally makes it harder`
			`# for people to get at the source code, and doesn't actually provide any`
			`# benefits that I am aware of.`
setup: add a setup.cfg file which instructs setuptools to install all eggs in unzipped form and to always copy them into the target directory (even if they are already installed somewhere else on the path that setuptools searches, which includes the CWD) 2008-01-22 13:46:47 -07:00			`zip_ok=False`
#249: get dependent libs from tahoe-deps and ../tahoe-deps 2008-09-16 18:36:27 -07:00
setup: update comments and URLs in setup.cfg 2010-05-03 23:16:53 -07:00			`# Tahoe-LAFS depends upon several libraries (foolscap, twisted, pycryptopp,`
			`# zfec, and others). Left to its own devices, setuptools will look on PyPI for`
			`# these and will download them at build time. The 'find_links=' entry in`
			`# setup.cfg causes setuptools to look for these dependent tarballs in`
			`# tahoe-deps/ and ../tahoe-deps/ before it resorts to downloading them from`
			`# PyPI.`
#249: get dependent libs from tahoe-deps and ../tahoe-deps 2008-09-16 18:36:27 -07:00
setup: update comments and URLs in setup.cfg 2010-05-03 23:16:53 -07:00			`# http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-deps.tar.gz contains a`
			`# bundle of these dependencies (as Python source distributions or "sdists"). So`
			`# it you want to avoid the build-time download (say, if you're on an airplane,`
setup: clarify the way that we host two directories of dependencies: one is source distributions and the other is binary distributions 2009-07-16 09:06:57 -07:00			`# or a desert island), just grab a copy and unpack it in your tahoe darcs tree.`
#249: get dependent libs from tahoe-deps and ../tahoe-deps 2008-09-16 18:36:27 -07:00
			`# Alternatively, if you're building from a release/nightly tarball instead of`
			`# a darcs tree, the 'sumo' tarball variant will include all of these`
			`# dependencies in the tahoe-deps/ directory.`

setup: Point setuptools at a directory on the allmydata.org test grid to find dependencies. Don't include an unrouteable IP address in find_links (fixes #574). 2009-01-11 09:11:26 -07:00			`find_links=misc/dependencies tahoe-deps ../tahoe-deps`
setup: update comments and URLs in setup.cfg 2010-05-03 23:16:53 -07:00			`http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-dep-sdists/`
			`http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/`
setup: comment-out the use of the directory full of dependency packages on the test grid -- the test grid is too unreliable! :-( 2009-03-06 22:43:32 -07:00
setup: update comments and URLs in setup.cfg 2010-05-03 23:16:53 -07:00			`# The following is a directory on the test grid which holds a bunch of packages`
			`# of dependencies. It is commented-out because the test grid has gone away and`
			`# a new one -- the Volunteer Test Grid -- is not yet publicly usable.`
setup: comment-out the use of the directory full of dependency packages on the test grid -- the test grid is too unreliable! :-( 2009-03-06 22:43:32 -07:00			`# http://testgrid.allmydata.org:3567/uri/URI%3ADIR2-RO%3Asnrfwfxatrci35zdgjnzxxx2ke%3Aunarxv347edtku3xzmefy4mcdmfngxzeb72iyqcadbjzjpczjx5a/index.html`
setup: attempt to remove the custom setuptools-ish logic in setup.py -- the result works on my Windows box but doesn't yield a working ./bin/tahoe on Windows, and hasn't been tested yet on other platforms 2008-12-05 17:30:54 -07:00
setup: configure setup.cfg to point setuptools at the index.html page instead of straight at the tahoe directory listing This is necessary, because if setuptools looks at the directory listing, then it follows the link named "More Info" in attempt to download the file, and this fails. 2009-01-14 12:50:23 -07:00			`# Other sites that we might want to list:`
setup: Point setuptools at a directory on the allmydata.org test grid to find dependencies. Don't include an unrouteable IP address in find_links (fixes #574). 2009-01-11 09:11:26 -07:00			`# http://sourceforge.net/project/showfiles.php?group_id=78018&package_id=79063`
setup: attempt to remove the custom setuptools-ish logic in setup.py -- the result works on my Windows box but doesn't yield a working ./bin/tahoe on Windows, and hasn't been tested yet on other platforms 2008-12-05 17:30:54 -07:00			`# http://pypi.python.org/pypi/pywin32`
setup: update comments and URLs in setup.cfg 2010-05-03 23:16:53 -07:00			`# (See http://tahoe-lafs.org/trac/tahoe-lafs/ticket/142 .)`
setup: attempt to remove the custom setuptools-ish logic in setup.py -- the result works on my Windows box but doesn't yield a working ./bin/tahoe on Windows, and hasn't been tested yet on other platforms 2008-12-05 17:30:54 -07:00
setup: use setup.cfg aliases to map "setup.py test" to "setup.py trial" and "setup.py build" to "setup.py darcsver --count-all-patches build_tahoe" Thanks to dpeterson for the suggestion. 2009-01-20 12:37:23 -07:00			`[aliases]`
setup: remove --multi-version It causes copious scary-looking warning messages and I'm no longer sure if it was actually needed to accomplish our goals ref #530. 2010-11-15 01:00:48 -08:00			`build = darcsver --count-all-patches develop --prefix=support make_executable build`
setup: setup.cfg aliases get expanded only once, so put everything you want to happen during the "test" step in the alias 2009-01-29 10:58:15 -07:00			`test = darcsver --count-all-patches develop --prefix=support make_executable build trial`
setup: invoke darcsver whenever doing an sdist 2009-01-29 10:51:25 -07:00			`sdist = darcsver --count-all-patches sdist`
setup: require darcsver >= 1.2.0 and rely exclusively on darcsver to set the version string 2009-01-29 12:56:40 -07:00			`install = darcsver --count-all-patches install`
			`bdist_egg = darcsver --count-all-patches bdist_egg`
setup: make sure you use darcsver whenever you are going to run trial This fixes the bug Brian had where he ran "python ./setup.py trial" and the allmydata-tahoe version number came out as 0.0.0. 2009-01-30 14:38:19 -07:00			`trial = darcsver --count-all-patches trial`
setup: if you sdist_dsc (to produce the input files for dpkg-buildpackage) then run darcsver first 2009-02-16 14:15:58 -07:00			`sdist_dsc = darcsver --count-all-patches sdist_dsc`
setup: add "test_mac_diskimage" command which attempts to mount and use a .dmg to make sure it has a good Tahoe distribution in it 2009-07-12 16:09:40 -07:00			`test_mac_diskimage = darcsver --count-all-patches test_mac_diskimage`