ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-20 21:43:09 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
05022dca36
tahoe-lafs/setup.cfg

48 lines
2.4 KiB
INI
Raw Normal View History

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 20:46:47 +00:00
[easy_install]
setup: update comments and URLs in setup.cfg
2010-05-04 06:16:53 +00: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 20:46:47 +00:00
zip_ok=False
#249: get dependent libs from tahoe-deps and ../tahoe-deps
2008-09-17 01:36:27 +00:00
setup: update comments and URLs in setup.cfg
2010-05-04 06:16:53 +00: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-17 01:36:27 +00:00
setup: update comments and URLs in setup.cfg
2010-05-04 06:16:53 +00: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 16:06:57 +00: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-17 01:36:27 +00: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 16:11:26 +00:00
find_links=misc/dependencies tahoe-deps ../tahoe-deps
setup: update comments and URLs in setup.cfg
2010-05-04 06:16:53 +00: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-07 05:43:32 +00:00
setup: update comments and URLs in setup.cfg
2010-05-04 06:16:53 +00: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-07 05:43:32 +00: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-06 00:30:54 +00: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 19:50:23 +00: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 16:11:26 +00: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-06 00:30:54 +00:00
# http://pypi.python.org/pypi/pywin32
setup: update comments and URLs in setup.cfg
2010-05-04 06:16:53 +00: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-06 00:30:54 +00: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 19:37:23 +00:00
[aliases]
setup: a new improved way to create tahoe executables Create the 'tahoe-script.py' file under the 'bin' directory. The 'tahoe-script.py' file is exactly the same as the 'tahoe-script.template' script except that the shebang line is rewritten to use our sys.executable for the interpreter. On Windows, create a tahoe.exe will execute it. On non-Windows, make a symlink to it from 'tahoe'. The tahoe.exe will be copied from the setuptools egg's cli.exe and this will work from a zip-safe and non-zip-safe setuptools egg.
2009-01-29 01:07:16 +00: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 17:58:15 +00:00
test = darcsver --count-all-patches develop --prefix=support make_executable build trial
setup: invoke darcsver whenever doing an sdist
2009-01-29 17:51:25 +00: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 19:56:40 +00: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 21:38:19 +00: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 21:15:58 +00: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 23:09:40 +00:00
test_mac_diskimage = darcsver --count-all-patches test_mac_diskimage
Reference in New Issue Copy Permalink