Eli System Administration Guide
Eli is distributed as source text, which must be configured and compiled before the system is usable. An extra (optional) installation step creates a library that takes advantage of versioned packages (see Versioned packages). There are two reasons for installing Eli:
As described in the Eli distribution's `README' file, you can build
the system by running
Installation will add the following files and directories to the specified directory (the `man', `bin', and `lib' sub-directories will be created by the installation process if they don't already exist):
Each package directory in these libraries contains a subdirectory for each distinct version of that package, plus meta-information defining the latest version. When a cache is built from a set of packages, the meta-information is used to establish links to the latest version in each set. The packages themselves are not copied to the cache.
When a new version of Eli is installed, the following changes are made to the libraries:
Locally-developed packages can be added to existing libraries, or new
libraries can be created to hold them.
A new library is typically created as a new subdirectory of the directory
specified by the
For example, you might create the directory `/opt/eli/Packages' to
hold additional packages that should be a part of the set from which every
cache was built.
If you then set the environment variable
You can add a package directory or package collection directory `dir' to a library directory `lib' by the following Eli request:
-> dir +d_dest=(lib) :installpkgDirectory `dir' must be built (if necessary) and all irrelevant files (e.g. `Makefile', `README', `CVS', source files) removed before this request is made. If `dir' is a package directory, it must contain `*.dg' and `version' files; if it is a package collection directory, it must contain a `PKGLST' file (see Versioned packages).
Packages installed via