When the Network Security Toolkit project moved from Red Hat
9 to Fedora Core 2 as
its base distribution, we created a branch under
CVS called rh9. This
allows us to continue patching/updating the Red Hat
9 version of the Network Security Toolkit if desired.
The following figures demonstrate how one can access the
source code under the rh9
CVS branch:
Figure 4.1. Anonymous Check Out of Red Hat 9 Branch
[root]#mkdir -p /usr/local/src/nst/rh9[root]#cd /usr/local/src/nst/rh9[rh9]#cvs -d:pserver:anonymous@nst.cvs.sourceforge.net:/cvsroot/nst loginLogging in to :pserver:anonymous@nst.cvs.sourceforge.net:2401/cvsroot/nst CVS password:PRESS ENTER KEY[rh9]#cvs -d:pserver:anonymous@nst.cvs.sourceforge.net:/cvsroot/nst checkout -r rh9 .... lots of output ...[rh9]#
Figure 4.2. Developer Check Out of Red Hat 9 Branch
[root]#mkdir -p /usr/local/src/nst/rh9[root]#cd /usr/local/src/nst/rh9[rh9]#export CVS_RSH=ssh[rh9]#export CVSROOT=:ext:USERID@nst.cvs.sourceforge.net:/cvsroot/nst[rh9]#cvs checkout -r rh9 .... lots of output ...[rh9]#
As a developer, any work you do in the
rh9 branch will be completely separate from
any work you do in the main development branch. You will need to
read up on the branch "merging" capabilities of
CVS if you want to merge changes from one
branch into another.
You can use the CVS
status command on any
CVS file to see what branch you are working
on. It reports branch information on the Sticky
Tag: line, but only if the file is part of a
branch.