Resolving Conflicts Using the CVS Client

Using the CVS Client 189 that have not been updated with the repository, CVS will inform you and give you the option of releasing the working directory. cd homelcp cvs release fuzion A banner.jpg M fuzion.pl You have [2] altered files in this repository. Are you sure you want to release directory `fuzion: Y rm –r fuzion

6.4.12 Tags and Releases

One of the strengths of CVS is its ability to create a release of a particular project. A release is a snapshot of a project at a specific point in time and is generally referred to by a numeric designation. When we refer to CVS version 1.1.11p1, we are talking about a specific release of the application that will always remain the same. If changes are made to that version of the software, the version number will change by indicating either a patch level or an incre- ment in the major or minor version number. This designation can be accomplished with CVS by assigning a tag to a project. Tags may be named in any fashion, symbolically with a numerical system as mentioned, or by code names, etc. It is important, however, that once a methodology for naming releases is established that it be abided by in order to prevent confusion in the future. To apply a tag to a project, issue the following command from within the project directory: cvs tag Release_1_1 . cvs server: Tagging . T 1.0.fuzion.pl T banner.jpg T em.dat T fuzion.pl T index.html T newfile T sk.dat T tal.dat T test.dat This does not change any information in the files; it simply places symbolic tags in the CVS repository so that when Release_1_1 of the Fuzion project is requested, these versions of the files will be retrieved from the repository. To check a specific release back out of the repository, issue the checkout command with the – r option and the name of the release. cvs checkout –r Release_1_1 fuzion 190 Chapter 6 • Introduction to CVS

6.5 Introduction to jCVS

For those more comfortable working with a GUI rather than a command line CVS client, there is a Java client available that uses Java that enables you to access off of the functionality of the CVS repository with a few clicks. jCVS was written by Timothy Gerard Endres and has been released under the GNU Public License GPL and may be found at http:www.jcvs.org.

6.5.1 System Requirements

As previously mentioned, jCVS will run on any platform supported by Java. The current release runs on Java version 1.2 or higher. The installed application is a little over 6MB with source code, so any computer capable of running Java and X should have not problems installing and running jCVS.

6.5.2 Installation Instructions

In order to run jCVS, you must first install the Java Runtime Environment. The latest and most complete runtime libraries available from Sun are http:java.sun.comj2se1.4down- load.html and can be found for Linux, Solaris and Windows. Download the installer for your platform and follow the instructions provided. This gener- ally consists of running an installer. In the example provided below, the jre was installed in usrlocaljre . Next, locate the latest jCVS tarball application archive. These are available at http: www.jcvs.orgdownload.html for download. For the purpose of these examples, assume that the application will be installed in usrlocaljcvs. cd tmp wget http:www.jcvs.orgdownloadjcvsjcvs-522.tgz --14:14:46-- http:www.jcvs.orgdownloadjcvsjcvs-522.tgz = `jcvs-522.tgz Connecting to www.jcvs.org:80... connected HTTP request sent, awaiting response... 200 OK Length: 1,976,228 [applicationx-tar] [snip] 14:14:55 226.81 KBs - `jcvs-522.tgz saved [1976228 1976228] cd usrlocal tar xzf tmpjcvs-522.tgz ln -s jCVS-5.2.2 jcvs usrlocaljrebinjava -jar \ usrlocaljcvsjarsjcvsii.jar