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

9000/7??:32* Series 700, 32-bit capable hardware required.
*:*64 64-bit capable hardware required.
*:32: 32-bit capable hardware required.
9000/7??:*64 Series 700, 64-bit capable hardware required.
9000/[78]??:32* Series 800, 32-bit capable hardware required.
9000/[78]??:*64 Series 800, 64-bit capable hardware required.
The value is matched against a target’s uname -m or getconf
_CS_HW_CPU_SUPP_BITS result.
os_name Defines the operating system(s) on which the files will run if a fileset
architecture has been defined. (If not specified, swpackage assigns a
value of *, meaning the files run on all operating systems.) If there are
multiple operating systems, use wildcards or use the ’|’ character to
separate them. This attribute should pattern match to the value of uname
-s or getconf KERNEL_BITS on the supported target systems.
os_release Defines the operating system release(s) on which the files will run. (If not
specified, swpackage 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 The version number of the operating system(s) on which the product will
run. If not specified, the attribute is assigned a value of *, meaning it runs
on any version. If there are multiple operating systems, use wildcards or
the | symbol to separate them. The value is matched against a target’s
uname -v result.
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 Optional keyword to end the fileset specification. No value is required. If
you place this keyword incorrectly, the file specification will fail.
10.4.2.4.9 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” (page 186).)
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.
188 Creating Software Packages