| 1 |
|
Using CVS (part 1) |
| 2 |
|
================== |
| 3 |
|
|
| 4 |
< |
tdb1, 18/10/2000 |
| 4 |
> |
Contents |
| 5 |
> |
-------- |
| 6 |
> |
- Overview |
| 7 |
> |
- CVS Repository Structure |
| 8 |
> |
- Setting up CVS on Raptor |
| 9 |
> |
- Setting up CVS on a Public PC (with WinCVS) |
| 10 |
> |
- Setting up CVS from off campus |
| 11 |
> |
- How to use CVS |
| 12 |
> |
|
| 13 |
> |
- See "Using CVS (part 2)" for information on binaries, |
| 14 |
> |
branching, tagging and keywords. |
| 15 |
|
|
| 16 |
+ |
tdb1, 18/10/2000 |
| 17 |
+ |
|
| 18 |
|
Overview |
| 19 |
|
-------- |
| 20 |
|
CVS means "Concurrent Versioning System" and is used to keep |
| 64 |
|
documentation |
| 65 |
|
minutes |
| 66 |
|
misc |
| 67 |
+ |
papers |
| 68 |
|
plan |
| 69 |
+ |
presentation |
| 70 |
|
specification |
| 71 |
|
user |
| 72 |
|
experimental |
| 88 |
|
|
| 89 |
|
We may need to expand that a bit, but it's a start. |
| 90 |
|
|
| 91 |
< |
Using CVS on Raptor |
| 92 |
< |
------------------- |
| 91 |
> |
Setting up CVS on Raptor |
| 92 |
> |
------------------------ |
| 93 |
|
Setting up CVS on raptor to use our "repository" takes a bit |
| 94 |
|
of effort. This is because the cs-sysadmin guys have been |
| 95 |
|
setting up CVS to run from marble, but it's not ready yet. |
| 116 |
|
to be able to do that ourselves... but by all means leave |
| 117 |
|
that line out if you feel happier. |
| 118 |
|
|
| 119 |
< |
|
| 120 |
< |
Using CVS on a Public PC (with WinCVS) |
| 107 |
< |
-------------------------------------- |
| 119 |
> |
Setting up CVS on a Public PC (with WinCVS) |
| 120 |
> |
------------------------------------------- |
| 121 |
|
WinCVS is (obviously) a Windows frontend to CVS. The command |
| 122 |
|
line thing is far easier to use if you're doing stuff |
| 123 |
|
directly on raptor (or any other unix box), but under |
| 148 |
|
|
| 149 |
|
Finally, it might be possible to get it working with SSH |
| 150 |
|
straight onto raptor, but I'm not sure of the exact process, |
| 151 |
< |
and even if it'll work. |
| 151 |
> |
and even if it'll work. I may add this as an errata in part2 |
| 152 |
> |
of this documentation. |
| 153 |
|
|
| 154 |
< |
Using CVS from off campus |
| 155 |
< |
------------------------- |
| 154 |
> |
Setting up CVS from off campus |
| 155 |
> |
------------------------------ |
| 156 |
|
Using CVS from off campus is much trickier. We have no |
| 157 |
|
"proper" CVS facilities on raptor for remote access (it can |
| 158 |
|
run a server specifically for this task). However, as the |
| 160 |
|
the firewall. This is fine if you have a Unix box at home, |
| 161 |
|
but I'm not sure (again) if this will work from Windows. |
| 162 |
|
|
| 163 |
+ |
From any Unix box (that has SSH and CVS installed) you just |
| 164 |
+ |
need to setup the following environment variables. These are |
| 165 |
+ |
best put in a file such as .cshrc (for the csh shell). |
| 166 |
+ |
|
| 167 |
+ |
CVS_RSH = |
| 168 |
+ |
ssh |
| 169 |
+ |
CVSROOT = |
| 170 |
+ |
:ext:user@raptor.ukc.ac.uk:/usr/local/proj/co600_10/cvs |
| 171 |
+ |
|
| 172 |
+ |
Every shell has it's own way of setting up environment |
| 173 |
+ |
variables, for example csh using the setenv command. Consult |
| 174 |
+ |
the man pages for more details. |
| 175 |
+ |
|
| 176 |
+ |
With this done you can use the command line facilities as |
| 177 |
+ |
usual, and you will be prompted for your raptor password |
| 178 |
+ |
each time a connection is made. |
| 179 |
+ |
|
| 180 |
|
How to use CVS |
| 181 |
|
-------------- |
| 182 |
|
There are three main CVS operations that you'll use on a |
| 185 |
|
describe them, then give an example. This all assumes you've |
| 186 |
|
setup the CVSROOT environment variable as described above. |
| 187 |
|
|
| 188 |
+ |
These commands are for the command line version of CVS, but |
| 189 |
+ |
the ideas can be applied to any version, including WinCVS. |
| 190 |
+ |
|
| 191 |
|
A full list of commands can be found by typing; |
| 192 |
|
|
| 193 |
|
cvs --help-commands |
| 310 |
|
|
| 311 |
|
That's just about it for basic CVS. I'll probably produce |
| 312 |
|
another document on tagging at some point in the future. |
| 313 |
+ |
|
| 314 |
+ |
About |
| 315 |
+ |
----- |
| 316 |
+ |
This document was written by Tim Bishop [tdb@i-scream.org] for |
| 317 |
+ |
use by the team working on a 3rd year Computer Science |
| 318 |
+ |
project called "i-scream". More details can be found on the |
| 319 |
+ |
project website; |
| 320 |
+ |
|
| 321 |
+ |
http://www.i-scream.org |
