 News |
FAQ
|
| Search
|
Home
|
| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
|
| Version 1.9 Build 1367 |
|
One of the main points to emerge from the tools exploder discussion and also the user specifications was that installation of aips++ must not require root privilege. This means that we cannot make use of certain unix system features which would greatly alleviate some problems, particularly in the area of initiating aips++ and network services.
Many aspects of installation are covered in part 2 of this document. One of the user requirements was that installation be easy. The intention is that installation of aips++ for supported architectures will at most consist of entering site and host information into editable ASCII site and host databases followed by a single make.
Installation of subsequent base releases should be even easier in one sense, since the databases will already be present. For sites undertaking their own code development, CVS provides a mechanism for merging their modifications with the new release code. Specific user or group ids will not be required for aips++ . However, we will recommend a set of aips++ user and group names and ids for those sites who wish to create a separate account for the aips++ package.
There is a potential conflict in requirements for access to aips++ , in that some sites will want to allow free access to all users, while others may want to restrict access to members of a particular group, particularly with regard to usage of data directories. This will affect the group ownership and permissions of the aips++ executables and data directories, and a procedure may have to be provided to reset these accordingly.