setup: clarify the way that we host two directories of dependencies: one is source...

diff --git a/setup.cfg b/setup.cfg
index f4d000988eabf3eeab0465fc9df6e716f1aab420..b6f549b8b96a514f04dcfef5ed5352e2a2f741e6 100644 (file)
--- a/setup.cfg
+++ b/setup.cfg
@@ -14,19 +14,21 @@ zip_ok=False
 # 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.
+# 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.
 
-# The directory on the allmydata.org testgrid is a directory where
-# tahoe developers host copies of upstream dependencies.
+# The directory on the allmydata.org testgrid named "tahoe-dep-sdists" is a
+# directory where tahoe developers host copies of upstream dependencies as
+# Python source distributions.  The one named "tahoe-dep-eggs" contains
+# Python binary distributions ("eggs").
 
 find_links=misc/dependencies tahoe-deps ../tahoe-deps
- http://allmydata.org/source/tahoe/deps/tahoe-deps/
+ http://allmydata.org/source/tahoe/deps/tahoe-dep-sdists/
  http://allmydata.org/source/tahoe/deps/tahoe-dep-eggs/
 
 # The following is a directory on the test grid which holds a bunch of packages of dependencies.