summaryrefslogtreecommitdiff
path: root/rdiff-backup
diff options
context:
space:
mode:
authorbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2002-12-07 19:02:29 +0000
committerbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2002-12-07 19:02:29 +0000
commit6e531149dc45115b875eed61d5aec13cf1055f5c (patch)
tree4412d2a7699a54fb2d30523cad9e731890b8ab80 /rdiff-backup
parent45a8046f785d4278a54af38f1895997b70ae68fe (diff)
downloadrdiff-backup-6e531149dc45115b875eed61d5aec13cf1055f5c.tar.gz
Clarified test instructions
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@241 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
Diffstat (limited to 'rdiff-backup')
-rw-r--r--rdiff-backup/CVS-README39
1 files changed, 26 insertions, 13 deletions
diff --git a/rdiff-backup/CVS-README b/rdiff-backup/CVS-README
index ecb0485..5b5a54c 100644
--- a/rdiff-backup/CVS-README
+++ b/rdiff-backup/CVS-README
@@ -5,12 +5,16 @@ Getting rdiff-backup to run:
----------------------------
If you want to run a version of rdiff-backup checked out of CVS into
-your $RDB_ROOT directory, change to $RDB_ROOT/rdiff_backup and run the
-./compilec.py file. With any luck, _librsync.so and C.so libraries
-will appear in that directory. Then run rdiff-backup, making sure
-that all the files are in your PYTHONPATH:
+your $RDB_CVS directory, change to $RDB_CVS/rdiff_backup and run the
+./compilec.py file:
-PYTHONPATH=$RDB_ROOT $RDB_ROOT/rdiff-backup
+ cd $RDB_CVS/rdiff_backup; python compilec.py
+
+With any luck, _librsync.so and C.so libraries will appear in that
+directory. Then run rdiff-backup, making sure that all the files are
+in your PYTHONPATH:
+
+ PYTHONPATH=$RDB_CVS $RDB_CVS/rdiff-backup <arguments>
Running the unit tests:
@@ -21,16 +25,25 @@ testfiles.tar.gz tarball. It is available at
http://rdiff-backup.stanford.edu/testfiles.tar.gz
-and untar it as root in the testing directory. Root is required
-because the tarball contains device files, files with various uid/gid,
-etc. If you don't have root, it's ok, all the tests except for
-roottest.py may still work.
+To untar it, root is required because the tarball contains device
+files, files with various uid/gid, etc. If you don't have root, it's
+ok, all the tests except for roottest.py may still work.
+
+So, three steps:
+
+1) Make sure the the C modules are compiled as explained above:
+
+ cd $RDB_CVS/rdiff_backup; python compilec.py
+
+2) Untar the testfiles tarball, as root if you have it:
-cd testing; tar -xvzf testfiles.tar.gz
+ cd $RDB_CVS/testing; tar -xvzf testfiles.tar.gz
-Then run the various *test.py files, for instance:
+3) In the testing directory, run each of the *test.py files as
+ desired. For instance,
-cd testing; python lazytest.py
+ cd $RDB_CVS/testing; python rpathtest.py
-If python restoretest.py doesn't work, try running ./makerestoretest3.
+ If python restoretest.py doesn't work, try running
+ ./makerestoretest3