Software Distributor Administration Guide (March 2009)

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 ” (page 227) for more information.) For example:
corequisites SD.data
prerequisites productA,r>=2.1
exrequisites productB,r>=2.1
NOTE: A dependency must always be specified using a software specification that
starts with the product tag for the requisite software.
You can specify multiple dependencies to define AND relationships between the
dependencies (AND meaning that all dependencies must be satisfied).
You can also define OR relationships using the or (|) character. The following rules
apply:
• White spaces are allowed around the OR character.
• OR dependencies are resolved from left to right.
Here is an example:
corequisite P.F
prerequisite ProdA | ProdB | ProdC.F | ProdC.FS
corequisite ProdX | ProdY | ProdZ | ProdW.FS
10.4 Creating a Product Specification File (PSF) 241