Sun/IRAF Site Manager's Guide

Sun/IRAF Site Manager's Guide

3.7. Configuring a custom LOCAL package

Anyone who uses IRAF enough will eventually want to add their own software to the system, by copying and modifying the distributed versions of programs, by obtaining and installing isolated programs written elsewhere, or by writing new programs of their own. A single user can do this by developing software for their own personal use, defining the necessary task statements etc. to run the software in their personal login.cl or loginuser.cl file. To go one step further and install the new software in IRAF so that it can be used by everyone at a site, one must configure a custom local package.

The procedures for configuring and maintaining a custom LOCAL package are similar to those outlined in §3.5 for installing and maintaining layered software, since a custom LOCAL will in fact be a layered software product, possibly even something one might want to export to another site (although custom LOCALs may contain non-portable or site specific software).

To make a custom local you make a copy of the "template local" package (iraf$local) somewhere outside the IRAF directory tree, change the name to whatever you wish to call the new layered package, and install it as outlined in §3.5. The purpose of the template local is to provide the framework necessary for a external package; a couple of simple tasks are provided in the template local to serve as examples. Once you have configured a local copy of the template local and gotten it to compile and link, it should be a simple matter to add new tasks to the existing framework.