 News |
FAQ
|
| Search
|
Home
|
| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
|
| Version 1.9 Build 1367 |
|
The AIPS++ code and system directories have been implemented essentially as described in the original documents. One issue which was not canvassed previously is the location of the RCS source code repositories. These have been implemented as a separate and parallel directory hierarchy under ãips++/master. At the moment the source code management consists of plain RCS, but this structure will readily accomodate CVS. Plain-text copies of the code are kept under the ãips++/code tree as originally planned.
Another point of departure from the original design has been to incorporate
the ftp directories directly under ãips++. This was prompted by
the realization that ãips++ could itself be NFS mounted under
tp, thereby circumventing the chroot limitation imposed by
anonymous ftp. All of AIPS++ is now available for access via this
method.
One modification required to meet this change was that of renaming the ftp directories so that they could be accomodated under ãips++. Certain other minor changes were also made, particularly with respect to the code distribution files. The structure currently resembles the following:
+--- import ----+---...
+- import_ftp --
|
| +--- install ---+----- cpp -----
| | +---- lwf_a ----
| |
| | +--- include ---
| | +-- implement --
| +--- kernel ----+--- scripts ---
| | +---- data -----
| | | +---- PBook ----
| | +----- doc -----+---- memos ----
| | +---- notes ----
| | +---- :
+---- code -----+
| +-- synthesis --+...
| +---- vlbi -----+...
| +---- dish -----+...
| +---- atnf -----+...
| +---- bima -----+...
| +---- drao -----+...
| +---- nfra -----+...
| +---- nral -----+...
| +---- nrao -----+...
| +---- tifr -----+...
| +--- contrib ---+...
|
+-- code_ftp ---
|
---+
| +--- install ---+----- cpp -----
| | +---- lwf_a ----
| |
| | +--- include ---
| | +-- implement --
| +--- kernel ----+--- scripts ---
| | +---- data -----
| | | +---- PBook ----
| | +----- doc -----+---- memos ----
| | +---- notes ----
| master | +---- :
+---- {rcs} ----+
| slave +-- synthesis --+...
| +---- vlbi -----+...
| +---- dish -----+...
| +---- atnf -----+...
| +---- :
|
+-- master_ftp -
|
:
:
A typical AIPS++ installation would only have the import and code subdirectories. Consortium sites would also have the import_ftp, and code_ftp subdirectories for redistribution of AIPS++ source code to local AIPS++ recipients. Consortium sites other than Charlottesville will also have a slave subdirectory containing a copy of the master RCS files. Charlottesville will instead have the master, and master_ftp subdirectories, the latter of which contains updates for the slave subdirectories at the other consortium sites.
All AIPS++ installations will have system directories with a structure similar to the following, except that only consortium sites will have ftp subdirectories:
:
:
|
+---- data -----+...
|
| +----- lib -----
| +--- libdbg ----
| |
| +----- bin -----
| +--- bindbg ----
| |
| +----- tmp -----
| +--- tmpdbg ----
| |
| +---- data -----
---+ |
| +---- apex -----+
| | | +---- ascii ---
| | | +---- info ----
| | +----- doc -----+---- manl ----
| | | +---- catl ----
| | | +---- :
| | |
| | | +---- msgs ----
+---- sun4 -----+ +--- (site1) ---+--- (host1) --
| | | +--- (host2) --
| | | +--- :
| | |
| | +--- (site2) ---+...
| | +--- :
| |
| +---- base -----+...
|
+-- sun4_ftp ---
|
+--- (arch2) ---+...
+- (arch2)_ftp -
+--- :
This hierarchy is identical to that originally envisaged.