Software Distributor Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (5900-2561, March 2013)

(Note that a corequisite dependency does not imply any “run-time
dependency” (load order). However, the corequisite dependency may affect
the fileset load order. This behavior can be controlled by the
loadorder_use_coreqs option. For more information on
loadorder_use_coreqs, see “Options Listed Alphabetically” (page 236).)
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 178) 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.2.4.10 Control Script Specification
SD-UX supports execution of product and fileset control scripts that allow you to perform additional
checks and operations with other HP-UX commands and functions. The swask, swinstall,
swconfig, swverify, and swremove commands each can execute one or more control scripts
on the primary roots. You can write the scripts and include them in your software package. All
scripts are optional but often are needed correctly complete the task that you want your software
package to perform. See Chapter 11: “Using Control Scripts ” (page 207) for a complete discussion
of control scripts.
10.4.2.4.11 File Specification
Within a fileset specification, you can specify the following file types to be packaged into the fileset
by swpackage:
• control script
• directory
• hard link
• regular file
• symbolic link
• archive
10.4 Creating a Product Specification File (PSF) 189