Defining Package Dependencies

You need to determine whether your package has dependencies on other packages and if any other packages depend on yours. Package dependencies and incompatibilities can be defined with two of the optional package information files, compver and depend. Delivering a compver file lets you name previous versions of your package that are compatible with the one being installed. Delivering a depend file lets you define three types of dependencies associated with your package. These dependency types are:

• A prerequisite package - meaning your package depends on the existence of another package

• A reverse dependency - meaning another package depends on the existence of your package

  ---

  Note -

  Use the reverse dependency type only when a package that cannot deliver a depend file relies on your package.

  ---

• An incompatible package (meaning your package is incompatible with the named package)

The depend file resolves only very basic dependencies. If your package depends upon a specific file or its contents or behavior, the depend file does not supply adequate precision. In this case a request script or (for the Solaris 2.5 and later operating environments) the checkinstall script should be used for detailed dependency checking. The checkinstall script is also the only script capable of cleanly halting the package installation process.

Be certain that your depend and compver files have entries in the prototype file. The file type should be i (for package information file).

Refer to the depend(4) and compver(4) man pages for more information.