HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
s
swpackage(4) swpackage(4)
(Hewlett-Packard Company)
os_release
Defines the operating system release(s) on which the files will run. (If not specified, swpack-
age
assigns a value of "*", meaning the files run on all releases.) If there are multiple operating
system releases, use wildcards or use the ’|’ character to separate them. This attribute should
pattern match to the value of uname -r on the supported target system(s).
os_version
Defines the operating system version(s) on which the files will run. (If not specified, swpack-
age
assigns a value of "*", meaning the files runs on all versions.) If there are multiple operat-
ing system versions, use wildcards or use the ’|’ character to separate them. This attribute
should pattern match to the value of uname -v on the supported target system(s).
revision
Defines the revision (release number, version number) of the fileset.
supersedes
Used when a patch is replaced by (or merged into) a later patch. The attribute indicates which
previous patches are replaced by the patch being installed or copied. This attribute value is a list
of software specifications of other patches that this patch "supersedes".
title
Defines the full name (one-line description) of the fileset.
end Ends the fileset specification. This keyword is optional.
Dependency Specification
You can add optional dependency information to a fileset definition if installation or execution of a fileset
depends on the presence or absence of another fileset:
prerequisites
A list of software that must be installed before the current fileset can be installed.
corequisites
A list of software that can be installed at the same time as the current fileset but must be
present before the current fileset can be run.
exrequisites
A list of software that may not be installed before or at the same time the current fileset is
installed.
If a dependency is not met, SD prevents the fileset from being installed.
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:
corequisite P.F
prerequisite ProdA | ProdB | BundleA | ProdC.FS
corequisite 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.
Section 4−−300 − 15 − HP-UX Release 11i: December 2000
___
___