mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2025-03-13 15:46:25 +00:00
0651991474
This is needed to allow virtualenv-based builds to exercise test_runner.BinTahoe (and a few others), which expect to run an executable program in "bin/tahoe". This also helps users who aren't yet accustomed to the new virtualenv world where they can just run "tahoe" instead of "bin/tahoe". This changes the "setup.py make_executable" command to copy the first "tahoe" executable found on $PATH into bin/tahoe . Previously bin/tahoe was created by modifying the shbang line of a template stored in bin/tahoe-script.template (which has been deleted). It also changes setup.cfg to run "make_executable" before tests, and *after* an install. Note that you must use "setup.py install" before "setup.py test", since make_executable requires the installed "tahoe" on $PATH. In the future, we hope to get rid of bin/tahoe altogether, and have these tests run the "tahoe" from $PATH directly.
42 lines
1.8 KiB
INI
42 lines
1.8 KiB
INI
[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.
|
|
|
|
# https://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
|
|
# source tree.
|
|
|
|
# Alternatively, if you're building from a release/nightly tarball instead of
|
|
# a git tree, the 'sumo' tarball variant will include all of these
|
|
# dependencies in the tahoe-deps/ directory.
|
|
|
|
find_links=misc/dependencies tahoe-deps ../tahoe-deps
|
|
https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-sdists/
|
|
https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/
|
|
|
|
# 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 ticket #142.)
|
|
|
|
[aliases]
|
|
build = update_version build
|
|
test = update_version build make_executable trial
|
|
sdist = update_version sdist
|
|
install = update_version install make_executable
|
|
bdist_egg = update_version bdist_egg
|
|
trial = update_version trial
|