Application Packaging Developer's Guide

Gathering Data With the checkinstall Script

The checkinstall script is executed shortly after the optional request script. It runs as the user install, if such a user exists, or the user nobody. The checkinstall script does not have the authority to change file system data; it is strictly a data gatherer. However, based on the information it gathers, it can create or modify environment variables in order to control the course of the resulting installation. It is also capable of cleanly halting the installation process.

The checkinstall script is intended to perform basic checks on a file system that would not be normal for the pkgadd command. For example, it can be used to check ahead to determine if any files from the current package are going to overwrite existing files, or manage general software dependencies (the depend file only manages package-level dependencies).

Unlike the request script, the checkinstall script is executed whether or not a response file is provided; and, its presence does not brand the package as “interactive.” This means that the checkinstall script can be used in situations where a request script is forbidden or administrative interaction is not practical.

Note –

The checkinstall script is available starting with the Solaris 2.5 and compatible releases.

checkinstall Script Behaviors

Design Rules for checkinstall Scripts