docs/quickstart.rst: swap two paragraphs to make it more likely a user will report import and versioning errors from 'bin/tahoe --version' if there are any, before trying to run tests. Also, change 'python setup.py test' to 'python setup.py trial' to avoid a rebuild that might change the dependencies (if setuptools decides to throw a spanner in the works).

This commit is contained in:
david-sarah 2012-09-14 02:10:12 +00:00
parent 15c95c2e12
commit 6c654be4d5
1 changed files with 3 additions and 3 deletions

View File

@ -60,13 +60,13 @@ On Windows, the ``build`` step might tell you to open a new Command Prompt
(or, on XP and earlier, to log out and back in again). This is needed the
first time you set up Tahoe-LAFS on a particular installation of Windows.
Optionally run ``python setup.py test`` to verify that it passes all of its
self-tests.
Run ``bin/tahoe --version`` (on Windows, ``bin\tahoe --version``) to verify
that the executable tool prints out the right version number after
"``allmydata-tahoe:``".
Optionally run ``python setup.py trial`` to verify that it passes all of its
self-tests.
Run Tahoe-LAFS
--------------