Using Packager and Installer for Linux and UNIX › Scripts within the Scope of Product Installation and Removal › Usage of Internal Procedures

Usage of Internal Procedures

Internal procedures are script files used to configure and interchange information with the product installation process. Internal procedures are part of the product; each of the script files must be defined in the file list of a component. Execute rights must have been specified for these script files.

You can create a new script file from the Packager GUI using the internal editor (which opens when you choose the Add New Files function.) Saving the new script file automatically adds its name to the file list of the component.

An existing script file is added to the file list of a component by using the Insert files function for the component of the PIF product.

If you want to add the internal procedure to a specific component, the procedure must be defined in that specific component (through the GUI or as an entry in the appropriate component section of the prototype file.) If you want to add the procedure to the product in general, the internal procedure can be defined for the product (through the GUI or as an entry in the product section in the prototype file.)

You can specify the following properties for internal procedures:

Execution Time

Execution time of the script. Possible values are as follows:

• pre installation—The script is executed before the package installation.
• post installation—The script is executed after the package installation.
• pre remove—The script is executed before the package is removed. If the script exits with a nonzero exit value, the component is not removed from the system, but the uninstallation process continues.
• post remove—The script is executed after the package has been removed.
• pre start—The script is executed before the product installation and any installation dialog starts.
• pre PIF install—A special script that is executed only the first time a product is installed on the target computer. Only this script is able to modify the product installation path.
• post interview—The script is executed after the interview phase (of the installation dialogs) has completed.
• post check—The script runs after the installer checks have been executed.

Options

If your script allows using command switches to configure the script execution, you can specify these switches when adding the internal procedure to the product. These command switches are applied to the script during script execution.

Interpreter

Optionally, you can specify an interpreter if the default interpreter, the shell, is not used.