# support/lib/ directory is gone.
fetch-and-unpack-deps:
- test -f tahoe-deps.tar.gz || wget http://allmydata.org/source/tahoe/tarballs/tahoe-deps.tar.gz
+ test -f tahoe-deps.tar.gz || wget http://allmydata.org/source/tahoe/deps/tahoe-deps.tar.gz
rm -rf tahoe-deps
tar xf tahoe-deps.tar.gz
automatically-installable dependencies; use the smaller regular tarball
if you don't mind the build process downloading the things it needs, or
if you've downloaded and unpacked the <tt><a
- href="http://allmydata.org/source/tahoe/tarballs/tahoe-deps.tar.gz">http://allmydata.org/source/tahoe/tarballs/tahoe-deps.tar.gz</a></tt>
+ href="http://allmydata.org/source/tahoe/deps/tahoe-deps.tar.gz">http://allmydata.org/source/tahoe/deps/tahoe-deps.tar.gz</a></tt>
bundle.</p>
# 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/tarballs/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.
+# 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.
# Alternatively, if you're building from a release/nightly tarball instead of
# a darcs tree, the 'sumo' tarball variant will include all of these