Software Distributor Administration Guide (March 2009)

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 237).)
240 Creating Software Packages