Download Erlang/OTP System Documentation

9.10 Releases
releases/ch_rel-1.rel
A new boot script was generated, without the local option set, before the release package was made. In the release
package, all application directories are placed under lib. You do not know where the release package will be installed,
so no hard-coded absolute paths are allowed.
The release resource file mysystem.rel is duplicated in the tar file. Originally, this file was only stored in the
releases directory to make it possible for the release_handler to extract this file separately. After unpacking
the tar file, release_handler would automatically copy the file to releases/FIRST. However, sometimes the
tar file is unpacked without involving the release_handler (for example, when unpacking the first target system)
and the file is therefore now instead duplicated in the tar file so no manual copying is necessary.
If a relup file and/or a system configuration file called sys.config is found, these files are also included in the
release package. See Release Handling.
Options can be set to make the release package include source code and the ERTS binary as well.
For information on how to install the first target system, using a release package, see System Principles. For information
on how to install a new release package in an existing system, see Release Handling.
9.10.5 Directory Structure
The directory structure for the code installed by the release handler from a release package is as follows:
$ROOT/lib/App1-AVsn1/ebin
/priv
/App2-AVsn2/ebin
/priv
...
/AppN-AVsnN/ebin
/priv
/erts-EVsn/bin
/releases/Vsn
/bin
•
•
•
•
lib - Application directories
erts-EVsn/bin - Erlang runtime system executables
releases/Vsn - .rel file and boot script start.boot; if present in the release package, relup and/or
sys.config
bin - Top-level Erlang runtime system executables
Applications are not required to be located under directory $ROOT/lib. Several installation directories, which contain
different parts of a system, can thus exist. For example, the previous example can be extended as follows:
$SECOND_ROOT/.../SApp1-SAVsn1/ebin
/priv
/SApp2-SAVsn2/ebin
/priv
...
/SAppN-SAVsnN/ebin
/priv
$THIRD_ROOT/TApp1-TAVsn1/ebin
/priv
/TApp2-TAVsn2/ebin
/priv
332 | Ericsson AB. All Rights Reserved.: Erlang/OTP System Documentation