| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
| Version 1.9 Build 874 |
|
Normally, AIPS++ programmers must belong to the AIPS++ programmer group in order to have permission to write to the AIPS++ source directories. The conventional name for this group is aips2prg (see §1.4), but it may be different at your site. Type
yourhost% groups
to list all groups that you are a member of, and consult your local AIPS++ manager if in doubt.
Apart from invoking aipsinit (p
), AIPS++ programmers need to create a
shadow copy of the AIPS++ code directory tree to serve as their
AIPS++ workspace. The mktree (p
) utility does this:
yourhost% mkdir $HOME/aips++ yourhost% cd $HOME/aips++ yourhost% mktree
Apart from creating a shadow copy of the AIPS++ code directory tree, mktree creates symbolic links into the AIPS++ rcs directory tree thereby linking the programmer's workspace to the local copy of the AIPS++ RCS repository (see §1.1.4).
mktree works incrementally so that if any workspace directories or
RCS symbolic links are accidently deleted, or if new AIPS++
directories are created, mktree will recreate only what is
necessary. For a more detailed description, see mktree (p
).
Once the programmer workspace has been created by mktree AIPS++
sources can be checked in and out, updated, renamed, or deleted by the
ai (p
), ao (p
), au (p
), amv (p
), and ax (p
)
utilities. Native RCS utilities such as rlog and
rcsdiff may also be used. For a more detailed description see
chapter 9.