| 1 |
|
Using CVS (part 2) |
| 2 |
|
================== |
| 3 |
|
|
| 4 |
< |
tdb1, 29/10/00. |
| 4 |
> |
Contents |
| 5 |
> |
-------- |
| 6 |
> |
- Errata to "Using CVS (part 1)" |
| 7 |
> |
- Setting up CVS on a Public PC (with WinCVS/SSH) |
| 8 |
> |
- Setting up CVS off campus/SSB (with WinCVS/SSH) |
| 9 |
> |
|
| 10 |
> |
- How CVS handles binary files |
| 11 |
> |
- Tagging the Repository |
| 12 |
> |
- Branching in CVS |
| 13 |
> |
- Keyword Expansion |
| 14 |
> |
- Online CVS Resources |
| 15 |
> |
|
| 16 |
> |
- See "Using CVS (part 1)" for basic information on setting |
| 17 |
> |
up and using CVS at UKC. |
| 18 |
|
|
| 19 |
+ |
tdb1, 29/10/00. |
| 20 |
+ |
|
| 21 |
|
Errata to "Using CVS (part 1)" |
| 22 |
|
------------------------------ |
| 23 |
|
Setting up CVS on a Public PC (with WinCVS/SSH) |
| 78 |
|
this time without the need for a mapped drive - which is a |
| 79 |
|
much neater way of doing things. |
| 80 |
|
|
| 81 |
+ |
Setting up CVS off campus/SSB (with WinCVS/SSH) |
| 82 |
+ |
----------------------------------------------- |
| 83 |
+ |
To do this you'll need two packages. Firstly, and most |
| 84 |
+ |
obviously WinCVS. The latest version of WinCVS (1.1b16) can |
| 85 |
+ |
be downloaded from the "WinCvs 1.1 *BETA* / Client + Local / |
| 86 |
+ |
Binaries" on the following page; |
| 87 |
+ |
|
| 88 |
+ |
http://www.wincvs.org/download.html |
| 89 |
+ |
|
| 90 |
+ |
Secondly you'll require SSH. I'm not sure where this package |
| 91 |
+ |
orginated, but there is a current version on raptor at; |
| 92 |
+ |
|
| 93 |
+ |
/usr/local/proj/co600_10/sshwin32/ssh-1.2.14-win32bin.zip |
| 94 |
+ |
|
| 95 |
+ |
Armed with those two files you're ready to go. To get |
| 96 |
+ |
started we need to get ssh installed, and a key setup with |
| 97 |
+ |
raptor. |
| 98 |
+ |
|
| 99 |
+ |
Installing ssh is easy. Simply extract the contents of the |
| 100 |
+ |
zip file in to your windows\system32 directory (on |
| 101 |
+ |
winnt/win2k - windows\system on win9x). This will put the |
| 102 |
+ |
DLL's in place and the binary ssh files. |
| 103 |
+ |
|
| 104 |
+ |
Next, setting up a key. This requires a few straightforward |
| 105 |
+ |
steps. |
| 106 |
+ |
|
| 107 |
+ |
- setup a directory to be considered your "home folder" and |
| 108 |
+ |
then ensure that the environment variable HOME is pointed |
| 109 |
+ |
at this directory. Then make a directory called .ssh |
| 110 |
+ |
within this. |
| 111 |
+ |
|
| 112 |
+ |
- telnet into raptor and run this command; |
| 113 |
+ |
ssh-keygen -f ssh-newkey -q -P '' -C '<user> on NT'" |
| 114 |
+ |
|
| 115 |
+ |
make sure you change <user> for your userid, and that you |
| 116 |
+ |
notice the difference between the single quote ' and the |
| 117 |
+ |
double quotes ". |
| 118 |
+ |
|
| 119 |
+ |
- using ftp (or by any other means) copy the files named |
| 120 |
+ |
ssh-newkey and ssh-newkey.pub to the .ssh folder you made |
| 121 |
+ |
on your machine. Now rename them to identity and |
| 122 |
+ |
identity.pub respectively. |
| 123 |
+ |
|
| 124 |
+ |
- Finally we need to get the contents of the identity.pub |
| 125 |
+ |
file above into the file ~/.ssh/authorized_keys on |
| 126 |
+ |
raptor. The easiest way to do this is to type the |
| 127 |
+ |
following; |
| 128 |
+ |
cat ssh-newkey.pub >> .ssh/authorized_keys |
| 129 |
+ |
|
| 130 |
+ |
This assumes you didn't delete the ssh-newkey files, and |
| 131 |
+ |
that you are in your home folder. Finally, you can delete |
| 132 |
+ |
the ssh-newkey and ssh-newkey.pub files from raptor. |
| 133 |
+ |
|
| 134 |
+ |
Now, to test this setup you should try the following from a |
| 135 |
+ |
command prompt; |
| 136 |
+ |
|
| 137 |
+ |
ssh -l <userid> raptor.ukc.ac.uk |
| 138 |
+ |
|
| 139 |
+ |
If everything has completed successfully you should now be |
| 140 |
+ |
looking at a raptor prompt. If not... then work out why not! |
| 141 |
+ |
|
| 142 |
+ |
Right, now on to WinCVS. This is now a doddle. In the |
| 143 |
+ |
preferences set the CVSROOT to; |
| 144 |
+ |
|
| 145 |
+ |
:ext:<user>@raptor.ukc.ac.uk:/usr/local/proj/co600_10/cvs |
| 146 |
+ |
|
| 147 |
+ |
Set Authentication to SSH server, and set the RSA identity |
| 148 |
+ |
to your identity file (not the .pub one). Finally set the |
| 149 |
+ |
browser directory to a suitable location and try checking |
| 150 |
+ |
something out. If all has worked an SSH window should pop up |
| 151 |
+ |
at the bottom of the screen and the files should appear. |
| 152 |
+ |
|
| 153 |
+ |
As a final note, turning TCP/IP compression on may make it |
| 154 |
+ |
quicker over a modem. |
| 155 |
+ |
|
| 156 |
|
How CVS handles binary files |
| 157 |
|
---------------------------- |
| 158 |
|
Basically CVS can't do version management of binary files, |
| 342 |
|
$Id$ |
| 343 |
|
|
| 344 |
|
$Log$ |
| 345 |
< |
Revision 1.1 2000/11/01 00:50:42 tdb |
| 346 |
< |
Checkin of second "Using CVS" paper, with keyword expansion turned off. |
| 345 |
> |
Revision 1.3 2000/11/15 20:03:48 tdb |
| 346 |
> |
Added a section on using WinCVS/SSH at home. |
| 347 |
|
|
| 348 |
|
Puts the latest log message in. |
| 349 |
|
|
