Difference between revisions of "Anonymous CVS"
| Line 20: | Line 20: | ||
in the directory to be updated (usually the <code>webwork2</code> directory or the <code>pg</code> directory). Typically a '-patches' or '-dev' release will be conservatively updated between releases to include bug fixes, but not new features. |
in the directory to be updated (usually the <code>webwork2</code> directory or the <code>pg</code> directory). Typically a '-patches' or '-dev' release will be conservatively updated between releases to include bug fixes, but not new features. |
||
| + | |||
| + | <code>-d</code> checks out new directories. <code>-P</code> deletes ("prunes") empty directories. |
||
Updates take place automatically except for the configuration files in the directory <code>conf</code>. Files such as <code>global.conf</code> and <code>database.conf</code> may need to be compared to the updated files <code>global.conf.dist</code> and <code>database.conf.dist</code> in order to manually make changes to the local configuration. |
Updates take place automatically except for the configuration files in the directory <code>conf</code>. Files such as <code>global.conf</code> and <code>database.conf</code> may need to be compared to the updated files <code>global.conf.dist</code> and <code>database.conf.dist</code> in order to manually make changes to the local configuration. |
||
| Line 25: | Line 27: | ||
cvs -n update -dP -r rel-2-1-patches |
cvs -n update -dP -r rel-2-1-patches |
||
| − | will show what files would change during an update with out actually changing the files. |
+ | will show what files would change during an update with out actually changing the files. You can also use this to determine which files you have modified locally. (They will be marked with an <code>M</code>.) The files which will be changed are preceeded by a letter. The letters stand for: |
| + | |||
| + | * <code>M</code> {{--}} The local copy of the file has been modified, but the CVS server's copy has not been changed. This indicates that you have made some local modifications to this file. |
||
| + | * <code>U</code> {{--}} A copy of this file will be downloaded from the CVS server |
||
| + | * <code>P</code> {{--}} The local copy of this file will be "patched" so that it agrees with the copy on the CVS server. This has the same affect as the U letter, but it is faster, since only portions of the file actually need to be downloaded in order to bring the local file up to date. |
||
| + | * <code>C<code> {{--}} There is a conflict between changes which you have made locally and changes which have been made on the CVS server file. If you update this file you will need to examine it with a text editor in order to reconcile the two different versions. (Search for the characters <code>======</code> {{--}} they indicate a region where changes have been made in both files.) |
||
| + | |||
| + | Files which have not been modified will not be listed. |
||
cvs update -dP -A |
cvs update -dP -A |
||
Revision as of 01:18, 2 March 2008
Our CVS repositories contain a complete history of WeBWorK and problem library development (since June 2001) as well as the latest bleeding-edge versions. They are available via the web or by using a CVS client.
To check out a module from CVS, run the following command:
cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/repository_name checkout module_name
Replace repository_name and module_name with values from the article List of CVS repositories hosted by The WeBWorK Project.
Examples
To check out the webwork2 and pg modules from the system repository, and the rochester_problib module from the rochester repository, type:
cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/system checkout webwork2 cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/system checkout pg cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/rochester checkout rochester_problib
To update to a new version, such as the version rel-2-1-patches, type:
cvs update -dP -r rel-2-1-patches
in the directory to be updated (usually the webwork2 directory or the pg directory). Typically a '-patches' or '-dev' release will be conservatively updated between releases to include bug fixes, but not new features.
-d checks out new directories. -P deletes ("prunes") empty directories.
Updates take place automatically except for the configuration files in the directory conf. Files such as global.conf and database.conf may need to be compared to the updated files global.conf.dist and database.conf.dist in order to manually make changes to the local configuration.
cvs -n update -dP -r rel-2-1-patches
will show what files would change during an update with out actually changing the files. You can also use this to determine which files you have modified locally. (They will be marked with an M.) The files which will be changed are preceeded by a letter. The letters stand for:
M— The local copy of the file has been modified, but the CVS server's copy has not been changed. This indicates that you have made some local modifications to this file.U— A copy of this file will be downloaded from the CVS serverP— The local copy of this file will be "patched" so that it agrees with the copy on the CVS server. This has the same affect as the U letter, but it is faster, since only portions of the file actually need to be downloaded in order to bring the local file up to date.C— There is a conflict between changes which you have made locally and changes which have been made on the CVS server file. If you update this file you will need to examine it with a text editor in order to reconcile the two different versions. (Search for the characters======— they indicate a region where changes have been made in both files.)
Files which have not been modified will not be listed.
cvs update -dP -A
will give you the very latest feature changes and bugs. Use cautiously.
cvs update -dP -r rel-2-1-patches
will take you back to the stable release.
Consult the CVS manual for more information on using CVS.
