Savannah - CVS

Public Areas:Main  |  Homepage  |  FAQ  |  Bugs  |  Support  |  Patches  |  Mailing Lists  |  Tasks  |  News  |  CVS  |  Files
   >>   Browse Sources CVS


Browsing the CVS Repository

You can Browse the CVS tree of this project with your web browser. This gives you a good picture of the current status of the source files. You may also view the complete histories of any file in the repository as well as differences among two versions.

Getting a Copy of the CVS Repository

CVS Newbies

If you've never used CVS, you should read some documentation about it; a useful URL is http://www.cvshome.org/ where you can find the Quick reference to CVS commands guide. Using CVS is not complex but you have to understand what is going on. The best way to start is to ask a friend to show you the way.

The basic informations described further on this page are detailled in the savannah user doc.

What are CVS modules?

The CVS repository of each project is divided into modules which you can download separately. The list of existing modules for this project can be obtained by looking at the root of the CVS repository; each File listed there is the name of a module, which can substitute the generic <modulename> used below in the examples of the co command of CVS. Note that . (dot) is always also a valid module name which stands for "all available modules" in a project. Most projects have a module with the same name of the project, where the main software development takes place.

The same applies to the Webpages Repository.

Anonymous CVS Access

This project\'s CVS repository can be checked out through anonymous (pserver) CVS with the following instruction set. The module you wish to check out must be specified as the modulename. When prompted for a password for anoncvs, simply press the Enter key.

Software repository:

cvs -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/savannah login

 
cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/savannah co <modulename>

Webpages repository:

cvs -d:pserver:anoncvs@subversions.gnu.org:/webcvs login

cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/webcvs co software/savannah

When you update from within the module's directory (with cvs update) you do not need the -d option anymore.

Developer CVS Access via SSH (Version 1, RSA)

Only project developers can access the CVS tree via this method. SSH1 must be installed on your client machine. If you have SSH version two, add

Host subversions.gnu.org
     Protocol 1
in your ~/.ssh/config file, even if you think that your SSH will switch to protocol 1 automatically. Substitute developername with the proper value. Your savannah password is useless for cvs. You have to register a CVS/SSH Shared key in the Account Maintenance page for the machine from which you run cvs.

Software repository:

export CVS_RSH=ssh

cvs -z3 -d<developername>@subversions.gnu.org:/cvsroot/savannah co <modulename>

Webpages repository:

export CVS_RSH=ssh

cvs -z3 -d<developername>@subversions.gnu.org:/webcvs co software/savannah

Developer CVS Access via Kerberos 5

Only project developers who also have a kerberos account on gnu.org can access the CVS tree via this method. CVS with GSSAPI support must be installed on your client machine (--with-gssapi --enable-encryption configure flags). Substitute developername with the proper value.

Software repository:

cvs -z3 -d:gserver:<developername>@subversions.gnu.org:/cvsroot/savannah co <modulename>

Webpages repository:

cvs -z3 -d:gserver:<developername>@subversions.gnu.org:/webcvs co /software/savannah

Symbolic Links in HTML CVS

Add a file named .symlinks in each directory where you want to make symbolic links. Each line of the file list a real file name followed by the name of the symbolic link. The symbolic links are built once a day. For more information check the documentation.

Import your CVS tree

If your project already has an existing CVS repository that you want to move to subversions, make an appointment with someone at cvs-hackers@gnu.org or savannah-hackers@gnu.org for the migration. You may want to read the Savannah administrator guidelines for this operation.

Firewall workaround

People living behind a fascist firewall can use the port 443 (https) to access the CVS tree with the :pserver: or :gserver: methods.

cvs -d ...subversions.gnu.org:443/cvsroot...

Compatibility

If your project was using subversions.gnu.org before Savannah was installed, you should know that Savannah does not impose any action nor does it break anything in your habits. Please refer to the generic mail providing all the information you may need on this subject.

Help!

You may take a look at the Savannah FAQ:
How do I import my project into the CVS (Sources)?
How do I upload my homepage (CVS HTML)?