swpackage.4 (2010 09)

s
swpackage(4) swpackage(4)
The following is an example of a dependency specification:
corequisites SD.data
...
prerequisites productA,r>=2.1
...
exrequisites productB,r>=2.1
...
Each keyword/value defines a dependency relationship on another software object. The object can be
within the same product as the dependent fileset, or it can be within another product.
Multiple dependency specifications are allowed. You can use them to define AND relationships between
the dependencies. (The AND relationship is implied because all dependencies must be satisfied.)
You can also define OR relationships using the ’|’ character. White spaces are not allowed around the OR
character, and OR dependencies are resolved from left to right. For example:
corequisites P.F
prerequisites ProdA|ProdB|BundleA|ProdC.FS
corequisites ProdX|ProdY|BundleZ|ProdW.FS
Note that if you specify a dependency for a fileset and the fileset is superseded by another fileset as part
of a patch, SD will still recognize the dependency.
Control Script Specification
Control scripts are often referred to as control_files, although control_files may include non-script files
such as space files, INDEX files, and INFO files.
Control_file syntax is:
control_file source [=tag][filename]
Where tag is the script name.
You can also list each item on a separate line:
control_file
source filename
tag tag_name
The following is an example of control script specifications:
checkinstall scripts/checkinstall
checkremove scripts/checkremove
configure scripts/configure
fix scripts/fix
postinstall scripts/postinstall
postremove scripts/postremove
preinstall scripts/preinstall
preremove scripts/preremove
request scripts/request
unconfigure scripts/unconfigure
unpostinstall scripts/postinstall
unpreinstall scripts/preinstall
verify scripts/verify
space space
For control scripts:
• Each script specification defines a control script object. The value of each keyword is the source
filename for the control file.
• Control scripts are optional. If present,
swpackage copies the specified source filename into
the depot’s storage directory for the associated product or fileset.
• You can use the keyword
control_file to define scripts or subscripts. If the basename of the
source path is a standard keyword, then SD executes that script. For example:
control_file scripts/script1=checkinstall
HP-UX 11i Version 3: September 2010 − 17 − Hewlett-Packard Company 17