From: Zooko O'Whielacronx <zooko@zooko.com>
Date: Sat, 13 Oct 2007 06:21:53 +0000 (-0700)
Subject: README: edit to clarify that you can't use "make" if you installed it the easy_instal... 
X-Git-Url: https://git.rkrishnan.org/pf/content/en/seg/priv.html?a=commitdiff_plain;h=97206487c3991564bbe03918649172ee52db7fb7;p=tahoe-lafs%2Ftahoe-lafs.git

README: edit to clarify that you can't use "make" if you installed it the easy_install way
---

diff --git a/README b/README
index 46fbfb29..f967db2c 100644
--- a/README
+++ b/README
@@ -208,12 +208,11 @@ Running-In-Place Way, and The Debian Way.  Choose one:
 
 TESTING THAT IT IS PROPERLY INSTALLED
 
- 'make check-deps' checks that all of the required Python package
- dependencies are installed.
-
- 'make test' runs the unit test suites.  (This can take a long time on
- slow computers.  There are a lot of tests and some of them do a lot of
- public-key cryptography.)
+ If you have gotten the source code, then you can run 'make check-deps'
+ checks that all of the required Python package dependencies are installed.
+ You can run 'make test' runs the unit test suites.  (This can take a long
+ time on slow computers.  There are a lot of tests and some of them do a lot
+ of public-key cryptography.)
 
  Executing the tahoe script from the "bin" subdirectory will work only if
  Tahoe itself is installed, either because it is installed into the local