Updated CVS_README

[BackupPC.git] / CVS_README

diff --git a/CVS_README b/CVS_README
index 8a061d4..782d4b7 100644 (file)
--- a/CVS_README
+++ b/CVS_README
@@ -21,14 +21,14 @@ Fetching CVS:
 
     mkdir somewhere/BackupPC
     cd somewhere/BackupPC
-    cvs -z3 -d:pserver:anonymous@cvs.backuppc.sourceforge.net:/cvsroot/backuppc co BackupPC
+    cvs -z3 -d:pserver:anonymous@backuppc.cvs.sourceforge.net:/cvsroot/backuppc co BackupPC
 
-* To fetch the CVS code tagged at a particular release (eg: v1.5.0):
+* To fetch the CVS code tagged at a particular release (eg: v2.1.2):
 
-    cvs -z3 -d:pserver:anonymous@cvs.backuppc.sourceforge.net:/cvsroot/backuppc co -r v1_5_0 BackupPC
+    cvs -z3 -d:pserver:anonymous@backuppc.cvs.sourceforge.net:/cvsroot/backuppc co -r v2_1_2 BackupPC
 
-Building an installable release from the source:
------------------------------------------------
+Building an installable release from the CVS source:
+---------------------------------------------------
 
 * Edit makeDist and set the version number and release date
 
@@ -38,6 +38,11 @@ Building an installable release from the source:
   all the library paths etc back into the symbolic form (eg: __INSTALLDIR__)
   so that configure.pl will do the right thing.
 
+  Often the language files are not up to date, and makeDist exits after
+  complaining about the lang files being inconsistent.  Use the -l option
+  to turn off that checking.
+
 * You should now have a sub-directory dist/BackupPC-version containing
-  the release and a tar ball dist/BackupPC-version.tar.gz.  The tar
-  ball can be copied, extracted and installed like any BackupPC release.
+  the release and a tar ball dist/BackupPC-VERSION.tar.gz.  The tar
+  ball can be copied, extracted and installed using configure.pl
+  like any BackupPC release.