| 52 |
|
documentation |
| 53 |
|
minutes |
| 54 |
|
misc |
| 55 |
+ |
papers |
| 56 |
|
plan |
| 57 |
+ |
presentation |
| 58 |
|
specification |
| 59 |
|
user |
| 60 |
|
experimental |
| 76 |
|
|
| 77 |
|
We may need to expand that a bit, but it's a start. |
| 78 |
|
|
| 79 |
< |
Using CVS on Raptor |
| 80 |
< |
------------------- |
| 79 |
> |
Setting up CVS on Raptor |
| 80 |
> |
------------------------ |
| 81 |
|
Setting up CVS on raptor to use our "repository" takes a bit |
| 82 |
|
of effort. This is because the cs-sysadmin guys have been |
| 83 |
|
setting up CVS to run from marble, but it's not ready yet. |
| 104 |
|
to be able to do that ourselves... but by all means leave |
| 105 |
|
that line out if you feel happier. |
| 106 |
|
|
| 107 |
< |
|
| 108 |
< |
Using CVS on a Public PC (with WinCVS) |
| 107 |
< |
-------------------------------------- |
| 107 |
> |
Setting up CVS on a Public PC (with WinCVS) |
| 108 |
> |
------------------------------------------- |
| 109 |
|
WinCVS is (obviously) a Windows frontend to CVS. The command |
| 110 |
|
line thing is far easier to use if you're doing stuff |
| 111 |
|
directly on raptor (or any other unix box), but under |
| 136 |
|
|
| 137 |
|
Finally, it might be possible to get it working with SSH |
| 138 |
|
straight onto raptor, but I'm not sure of the exact process, |
| 139 |
< |
and even if it'll work. |
| 139 |
> |
and even if it'll work. I may add this as an errata in part2 |
| 140 |
> |
of this documentation. |
| 141 |
|
|
| 142 |
< |
Using CVS from off campus |
| 143 |
< |
------------------------- |
| 142 |
> |
Setting up CVS from off campus |
| 143 |
> |
------------------------------ |
| 144 |
|
Using CVS from off campus is much trickier. We have no |
| 145 |
|
"proper" CVS facilities on raptor for remote access (it can |
| 146 |
|
run a server specifically for this task). However, as the |
| 148 |
|
the firewall. This is fine if you have a Unix box at home, |
| 149 |
|
but I'm not sure (again) if this will work from Windows. |
| 150 |
|
|
| 151 |
+ |
From any Unix box (that has SSH and CVS installed) you just |
| 152 |
+ |
need to setup the following environment variables. These are |
| 153 |
+ |
best put in a file such as .cshrc (for the csh shell). |
| 154 |
+ |
|
| 155 |
+ |
CVS_RSH = |
| 156 |
+ |
ssh |
| 157 |
+ |
CVSROOT = |
| 158 |
+ |
:ext:user@raptor.ukc.ac.uk:/usr/local/proj/co600_10/cvs |
| 159 |
+ |
|
| 160 |
+ |
Every shell has it's own way of setting up environment |
| 161 |
+ |
variables, for example csh using the setenv command. Consult |
| 162 |
+ |
the man pages for more details. |
| 163 |
+ |
|
| 164 |
+ |
With this done you can use the command line facilities as |
| 165 |
+ |
usual, and you will be prompted for your raptor password |
| 166 |
+ |
each time a connection is made. |
| 167 |
+ |
|
| 168 |
|
How to use CVS |
| 169 |
|
-------------- |
| 170 |
|
There are three main CVS operations that you'll use on a |
| 172 |
|
smaller commands such as add, delete, and export. I'll |
| 173 |
|
describe them, then give an example. This all assumes you've |
| 174 |
|
setup the CVSROOT environment variable as described above. |
| 175 |
+ |
|
| 176 |
+ |
These commands are for the command line version of CVS, but |
| 177 |
+ |
the ideas can be applied to any version, including WinCVS. |
| 178 |
|
|
| 179 |
|
A full list of commands can be found by typing; |
| 180 |
|
|
