Software Distributor Administration Guide for HP-UX 11i

Creating Software Packages
Creating a Product Specification File (PSF)
Chapter 10 335
Dependency Specification The swinstall, swcopy, swverify, and
swremove commands recognize software dependencies. The default
behavior for swinstall, for example, prevents an install unless all
dependencies are met.
The PSF specifies dependencies between filesets. Dependencies are
defined within the fileset class definition. (See “Fileset Specification” on
page 331.)
You can also define dependencies between:
• A fileset and another product (namely, a subset of that product).
• A particular fileset within that product.
• The entire product.
SD-UX supports these types of dependencies:
Corequisite Software that must be present for a fileset to operate
correctly. For example, specifying a corequisite for an
install fileset means that the corequisite must be
installed or being installed when the fileset itself is
installed.
(Note that a corequisite dependency does not imply any
“run-time dependency” (load order).)
Exrerequisite Software that may not be present when the fileset is
operated on by SD-UX. For example, specifying an
exrequisite for a fileset prevents the fileset from being
installed if any of the specified exrequisite software
objects are installed or are being installed.
Prerequisite Software that must be installed and/or configured
correctly before a fileset can be operated on by SD-UX.
Prerequisites control the order of an installation with
swinstall (install-time dependency).
Dependencies are specified as a software_specification value type within
the PSF. (See “PSF Value Types” on page 317 for more information.) For
example:
corequisites SD.data
prerequisites productA,r>=2.1
exrequisites productB,r>=2.1