![]() | Getting Started |
Prev | Next |
In this section we assume that you are using CVS only on the client side. That means, someone (probably the administrator of the CVS repository) gave you an account on the server machine, and it's your job to checkout modules from the repository and work with them.
CVS supports several methods of accessing the repository, which can be categorized as follows:
The repository is something like /home/cvs and is simply stored in a folder which is accessible from your computer. It may physically be on a disk which is mounted via NFS, but this is an irrelevant detail. If you often use a certain local repository, you will want to tell Cervisia about it.
Procedure 1.1. Adding A Local Repository
Open the Repositories dialog by choosing Repository->Repositories....
Press the Add... button.
Enter the details of the repository in the dialog box that displays.
Confirm by pressing the OK button.
In the future, whenever you use Cervisia to check out a new module, Cervisia will present you the repositories you have added here.
The repository name is something like :ext:bernd@cvs.cervisia.sourceforge.net:/cvsroot/cervisia.
This method requires that you have a user account on the server machine (in this case, cvs.sourceforge.net and use a remote shell for communication. By default, CVS uses rsh for this purpose, however, rsh is long considered to be insecure, and is widely replaced by ssh.
If you must use ssh, you must set the environment variable $CVS_RSH to ssh when using the cvs client. Cervisia supports this easily.
Open the repositories dialog again, and press the Add... button. Now enter the name of the repository in the first line and the remote shell (e.g. ssh) in the second line. If you now confirm with the OK button, Cervisia memorizes these settings.
Note that Cervisia can not answer possible password requests from the server machine. You must make sure that a remote login works without requiring you to enter the password. With plain vanilla rsh, this can be achieved for example by creating a $HOME/.rhosts file with a list of trusted hosts (see the rsh manpage).
With ssh, it can be achieved by copying your public key $HOME/.ssh/identity.pub to the server. In this case, the key must not be encrypted with a passphrase (see the ssh> manpage and the CVS/SSH FAQ on SourceForge). If you are unsure about these issues, ask your system administrator.
The repository name looks like :pserver:gehrmab@cvs.kde.org:/home/kde
This method accesses the server via a special protocol with a relatively weak authentication (pserver stands for password authentication). Before you can use such a server, you have to login. As this is not directly supported by Cervisia, enter on the command line
%cvs -d :pserver:joe@cvs.kde.org:/home/kde login
(of course, with your repository substituted). CVS will prompt you for your password and check with the server. If the password is ok, the repository name, together with the (slightly scrambled) password, will be appended to the file $HOME/.cvspass. Whenever CVS accesses the repository, it will silently send the password to the server, so you do not have to take care of that once you have logged in. As everybody who knows your password can work with the repository in your name (and even do major damage to it), you should keep the $HOME/.cvspass secret and non-readable for others.
Prev | Home | Next |
Cervisia Manual | Up | Importing a module into the repository |