1 #========================================================================
3 # CVS_README - CVS README file for BackupPC.
6 # Instructions for using CVS
9 # Craig Barratt <cbarratt@users.sourceforge.net>
11 #========================================================================
13 # See http://backuppc.sourceforge.net.
15 #========================================================================
20 * To fetch the current CVS code run this commands:
22 mkdir somewhere/BackupPC
24 cvs -z3 -d:pserver:anonymous@backuppc.cvs.sourceforge.net:/cvsroot/backuppc co BackupPC
26 * To fetch the CVS code tagged at a particular release (eg: v3.2.0):
28 cvs -z3 -d:pserver:anonymous@backuppc.cvs.sourceforge.net:/cvsroot/backuppc co -r v3_2_0 BackupPC
30 Building an installable release from the CVS source:
31 ---------------------------------------------------
33 * Update makeDist and configure.pl if you add any new files to the release.
35 * Run makeDist, using arguments to specify the release date and version:
37 makeDist --releasedate '29 Mar 2009' --version 3.2.0beta0
39 makeDist merges the version number, release date and turns all the
40 library paths etc back into the symbolic form (eg: __INSTALLDIR__)
41 so that configure.pl will do the right thing.
43 Sometime the language files are not up to date, and makeDist exits
44 after complaining about the lang files being inconsistent. Use
45 the --nolangCheck option to turn off that checking.
47 By default makeDist does a syntax check on all the source files.
48 If you want to skip that you can use tune --nosyntaxCheck option, eg:
50 makeDist --nolangCheck --nosyntaxCheck --releasedate '31 Jul 2010' --version 3.2.0
52 * You should now have a sub-directory dist/BackupPC-VERSION containing
53 the release and a tar ball dist/BackupPC-VERSION.tar.gz. You can
54 cd to dist/BackupPC-VERSION and run configure.pl from there, or
55 the tar ball can be copied, extracted and installed using configure.pl
56 like any BackupPC release.