| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
| Version 1.9 Build 874 |
|
The AIPS++ RCS directories are maintained only at AIPS++ code development sites. They are not provided with the end-user AIPS++ distribution.
The one true AIPS++ master RCS repository resides on host aips2.nrao.edu at NRAO's Array Operations Center in Socorro, New Mexico, USA. This is the working copy for AIPS++ code management, consortium sites access this one way or another for checkin and checkout (see §9).
The master RCS directory hierarchy is the same as the code
hierarchy described above except that the master has an etc
subdirectory which is used for central administrative purposes (see
§13). In order to reduce the amount of network traffic
involved in a checkin/out the master only contains revisions for the current
and preceding major AIPS++ version numbers (see avers (p
)). A separate
archive repository contains all revisions other than those for the
current major version number.
: +--- etc -----
: |
| | +--- apps ----+...
| | +- implement -+...
| +--- aips ----+-- fortran --+...
| | +-- scripts --
| | +--- data ----
+-- master ---+
| +--- dish ----+...
| +- synthesis -+...
| +--- vlbi ----+...
| +-- contrib --+...
| :
---------+
| +--- etc -----
| |
| | +--- apps ----+...
| | +- implement -+...
| +--- aips ----+-- fortran --+...
| | +-- scripts --
| | +--- data ----
+-- archive --+
| +--- dish ----+...
| +- synthesis -+...
| +--- vlbi ----+...
: +-- contrib --+...
: :
Most AIPS++ consortium sites have the master RCS repository remotely NFS mounted beneath $AIPSROOT, and some also maintain a copy of the archive repository.
All AIPS++ consortium sites, including that at Socorro, maintain a slave RCS repository which is regularly updated by the AIPS++ code distribution system (§8) so that it keeps track of the master (aside from the master/etc directory). This slave RCS repository is used to update the plain-text code directories (§1.1.1).
The AIPS++ makefiles (p
) only ever refer to the RCS repositories
indirectly, through a symbolic link called rcs which usually points to
slave but could, in principle, be switched to point to master or
archive.
:
:
+- (master) --+...
+- (archive) -+...
| +--- apps ----+...
| +- implement -+...
| +--- aips ----+-- fortran --+...
| | +-- scripts --
+---- rcs | +--- data ----
| = |
/aips++ -+--- slave ---+
| +--- dish ----+...
| +- synthesis -+...
| +--- vlbi ----+...
: +-- contrib --+...
: :
inhale (p
) creates a tmp directory beneath the slave
directory for the duration of its operation.