changeset 1122:7ea7ebf9b5b5

Fixed indention.
author Martin Geisler <mg@daimi.au.dk>
date Tue, 10 Mar 2009 09:18:30 +0100
parents b74f7081ff81
children 3d739e0e2e17
files doc/install.txt
diffstat 1 files changed, 15 insertions(+), 15 deletions(-) [+]
line wrap: on
line diff
--- a/doc/install.txt	Tue Mar 10 09:16:46 2009 +0100
+++ b/doc/install.txt	Tue Mar 10 09:18:30 2009 +0100
@@ -74,36 +74,36 @@
    up-to-date).
 
 2) Download and Install Twisted_ from source. There is an installer
-  for Mac OS X 10.5 which can be used if you use Mac OS X 10.5. Notice
-  again that Mac OS X comes with a pre-installed version of Twisted,
-  but this is not the full Twisted installation. After installation
-  change your ``PYTHONPATH`` (in your ``~/.bash_profile``) to::
+   for Mac OS X 10.5 which can be used if you use Mac OS X
+   10.5. Notice again that Mac OS X comes with a pre-installed version
+   of Twisted, but this is not the full Twisted installation. After
+   installation change your ``PYTHONPATH`` (in your
+   ``~/.bash_profile``) to::
 
       export PYTHONPATH="/Library/Python/2.5/site-packages:${PYTHONPATH}"
-
       export PYTHONPATH=$PYTHONPATH:$HOME/opt/lib/python
 
 3) Optionally: download PyOpenSSL_ and tell us if it works!
 
 4) Download and install GMP_. You can preferably use the Macports or
-  Fink package utilities. If you download the other dependencies from
-  either Macports or Fink, they might depend on Python 2.4 which is
-  not preferable, you should use Python 2.5, unless you have good
-  reasons not to.
+   Fink package utilities. If you download the other dependencies from
+   either Macports or Fink, they might depend on Python 2.4 which is
+   not preferable, you should use Python 2.5, unless you have good
+   reasons not to.
 
 5) Download and install GMPY_ following the instructions in
    ``gmpy-1.02.macosx.README.txt`` (under Downloads).
 
 6) Install VIFF from source (see below). If you prefer you can just
-  install it in site-packages, it makes no difference.
+   install it in site-packages, it makes no difference.
 
-  For developers, either add VIFF to the PYTHONPATH::
+   For developers, either add VIFF to the PYTHONPATH::
 
-    export PYTHONPATH=$PYTHONPATH:$HOME/path-to-viff/viff
+      export PYTHONPATH=$PYTHONPATH:$HOME/path-to-viff/viff
 
-  or create a symbolic link from the site-packages directory to the
-  VIFF Python files (``viff/viff/``), as otherwise you need to
-  re-install VIFF each time the project is modified.
+   or create a symbolic link from the site-packages directory to the
+   VIFF Python files (``viff/viff/``), as otherwise you need to
+   re-install VIFF each time the project is modified.
 
 7) Proceed to `testing`_.