---

Arguments and Environment Variables for Install Operations

The following list describes the arguments and environment variables available to install operation executables. Note that not all environment variables are available to all executables (see Table 7-2).

• $1: Full path to the installation package the Installer application is processing. For example:

  /Volumes/Users/michelle/Desktop/Levon.mpkg

• $2: Full path to the installation destination. For example:

  /Applications

• $3: Installation volume (or mountpoint) to receive the payload. For example:

  /

  /Volumes/Tools

• $4: The root directory for the system:

  /

• $SCRIPT_NAME: Filename of the operation executable. For example:

  preflight

• $PACKAGE_PATH: Full path to the installation package. Same as $1.

• $INSTALLER_TEMP: Scratch directory used by Installer to place its temporary work files. Install operations may use this area for their temporary work, too, but must not overwrite any Installer files. The Installer application erases this directory at the end of the install. For example:

  /private/tmp/.Levon.pkg.897.install

• $RECEIPT_PATH: Full path to a temporary directory containing the operation executable. This is a subdirectory of $INSTALLER_TEMP. This location may vary between installs. The executable can use this path to locate other files in the package. For example:

  /private/tmp/.Levon.pkg.897.install/Receipts/Levon.pkg/Contents/Resources

The four arguments described earlier are available to all install operations. Table 7-2 shows the availability of the environment variables.

---