Software Packager for Linux and UNIX › Define Dependencies

Define Dependencies

The installation of a PIF package can depend on the presence or absence of another product or product version on the target computer. Such a dependency can exist between the PIF package to install and another UNIX product in the PIF, PKG, or RPM packaging format.

Dependencies of PIF packages can be one of the following types:

Mandatory dependency

A product prod1 is mandatory dependent on product prod2, when prod2 must be installed on the target computer before product prod1 is installed. If prod2 is not installed, the Installer automatically searches for it, using a specific algorithm, and installs it if found. If the Installer cannot find prod2, the installation is aborted. Prod2 is called required product.

Incompatible dependency

A product prod1 is incompatible dependent on product prod2, when prod2 must not be installed on the target computer when product prod1 is installed. If prod2 is installed, the installation of prod1 is aborted.

Optional dependency

A product prod1 is optional dependent on a product prod2, when prod2 is not mandatory required before prod1 is installed. Prod2 is installed on the target computer only on user demand. If a previous version of prod2 already exists on the target computer, it is updated to the new version.

1. Select the package on the project pane.
2. Select the Dependencies tab.

   A list of the currently required products appears in the subproject pane.

3. Right-click in this list and select Add from the context menu.

   The Product dependency dialog appears.

4. Specify properties of the required product as follows:

   Product name

   Indicates the name of the required product, that is, the product to which the dependency exists. Type the name or click the browse button (...) to browse for the product and import its name automatically.

   Product version

   Indicates the version of the required product.

   Dependency type

   Indicates the type of dependency between the products. Select a type from the drop-down list.

   Operator

   Indicates the version operator that supplements the entered product version and specifies the dependency to a range of product versions, for example, to all product versions equal to or newer as (>=) the entered product version. Select an operator from the drop-down list.

   Installation behavior

   (For dependency type Optional only.) Determines whether the required product is installed always (install) or only on demand (do not install).

5. Click Add.

   The dependency definition is added to the prototype file. The new dependency is displayed on the Dependencies tab.