X-Git-Url: https://git.rkrishnan.org/?a=blobdiff_plain;f=setup.cfg;h=ac312c9d2be7b434f2c8e25306efdc069348790a;hb=HEAD;hp=c38775075541a4b9e65661d4e8511b4c92638e4d;hpb=c1e3c66db206e5c117995e426af4e7c759a788d7;p=tahoe-lafs%2Ftahoe-lafs.git diff --git a/setup.cfg b/setup.cfg index c3877507..ac312c9d 100644 --- a/setup.cfg +++ b/setup.cfg @@ -1,28 +1,41 @@ [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 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. +# 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://allmydata.org/source/tahoe/deps/tahoe-deps.tar.gz contains a bundle -# of these dependencies. 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. +# 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 darcs tree, the 'sumo' tarball variant will include all of these +# a git tree, the 'sumo' tarball variant will include all of these # dependencies in the tahoe-deps/ directory. -# The directory on the allmydata.org testgrid is a directory where -# tahoe developers host copies of upstream dependencies. - find_links=misc/dependencies tahoe-deps ../tahoe-deps - http://testgrid.allmydata.org:3567/uri/URI%3ADIR2-RO%3Asnrfwfxatrci35zdgjnzxxx2ke%3Aunarxv347edtku3xzmefy4mcdmfngxzeb72iyqcadbjzjpczjx5a/ + 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 develop --prefix=support make_executable build +test = update_version develop --prefix=support make_executable build trial +sdist = update_version sdist +install = update_version install +bdist_egg = update_version bdist_egg +trial = update_version trial