GCC: Anonymous read-only rsync access

In an ongoing effort to accelerate development of GCC and provide an open development environment, we are offering our CVS repository and various other data through anonymous rsync access.

That way you can make local copies of the GCC CVS repository to ease the burden on the GCC main site, and browse the source locally using cvs.

Using rsync

The GCC repository is available at rsync://gcc.gnu.org/gcc-cvs. The whole repository takes over 1.2G of disk space, which takes a substantial time to transfer. Subsequent synchronizations will be much faster, though, as rsync uses a smart algorithm to only transfer differences over the network.

Here is how you get a copy of the repository:

rsync --archive --delete --compress \
      --exclude '#cvs.*' --exclude 'CVSROOT/config' \
      --exclude 'CVSROOT/history' --exclude 'CVSROOT/updatelog' \
      rsync://gcc.gnu.org/gcc-cvs gcc-cvs

The same command can be run periodically to synchronize your copy of the repository.

Other rsync options that you might want to use include --verbose and --progress to provide feedback, including during the initial phase that is otherwise silent.

You can get rsync from its home page, rsync.samba.org.

To get a list of available rsync targets, run:

rsync rsync://gcc.gnu.org/

Other interesting data, such as the GCC ftp directories, is also available.

Using the local repository

Refer to CVS instructions to check out your local copy of the repository.

If your new repository is local to the system where you'll check out a copy then you'll define CVSROOT in your environment to be the full pathname of its gcc-cvs directory. If it's on another system then you'll define CVSROOT to be :ext:user@host:path. By default CVS will use rsh to access the remote repository, but you can use ssh instead by setting the environment variable CVS_RSH to ssh.

Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways to contact the FSF.

These pages are maintained by the GCC team.

For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the gcc-help@gcc.gnu.org mailing list might help.
Please send comments on these web pages and the development of GCC to our developer mailing list at gcc@gnu.org or gcc@gcc.gnu.org. All of our lists have public archives.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

Last modified 2004-12-28