| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
| Version 1.9 Build 874 |
|
It is more difficult to setup things to contribute to the AIPS++ data repository than to mirror it. The first requirement is that the user must have an account on the AIPS++ central server, aips2.nrao.edu, and the user id on aips2.nrao.edu must be a member of the aips2prg group. In addition, CVS and SSH must be installed on your local system. These packages are widely available.
With ssh you create your pair of keys using ssh-keygen.
This will create ~/.ssh/identity.pub on your local machine
(or ~/.ssh/id_dsa.pub for ssh2 based versions)
You then add the contents of this file to ~/.ssh/authorized_keys
(~/.ssh/authorized_keys2 for ssh2 based)
on aips2.nrao.edu.Make sure authorized_keys is readable only by
the user. After that, you are ready to try ssh; try something like:
yourhost% ssh aips2.nrao.edu which cvs yourhost% ssh aips2.nrao.edu which co
from your local machine. You must get these to return the path to the
cvs and co binaries before going further. These binaries
are located in /opt/local/gnu/bin on aips2.nrao.edu. To make
this path available, you may need to edit ~/.ssh/environment on
aips2.nrao.edu, and add a line like:
PATH=/usr/bin:/opt/local/bin:/opt/local/gnu/bin
Shell variables, e.g. $PATH, are not expanded.
Once you have resolved all of the problems involved with running remote commands on aips2.nrao.edu, you are ready to check out a piece of the data repository. First you must tell your local cvs installation to go to aips2.nrao.edu for the repository and to use ssh instead of rsh to run remote commands. For the Bourne-like shells, you do this like:
yourhost% CVS_RSH=ssh
yourhost% CVSROOT=:ext:aips2.nrao.edu:/aips++/cvs
yourhost% export CVS_RSH CVSROOT
for C-like shells, you would do:
yourhost% setenv CVS_RSH ssh
yourhost% setenv CVSROOT :ext:aips2.nrao.edu:/aips++/cvs
Now to check out a piece of the source from which the data repository is built, you would do something like:
yourhost% cvs co data/nrao
This would check out the data specific to NRAO. Unlike RCS, when you check out files from CVS the files are not locked. Other users can check out and check in changes to the same files. Checking out the files just provides a copy of the current state of the files to work with. Any conflicts between your changes and changes which have occurred since you checked out the files are addressed at check in time (actually cvs update time).