swpackage.4 (2010 09)

s
swpackage(4) swpackage(4)
[ <file specifications> ]
end
Each keyword defines an attribute of a fileset object. For each fileset specified,
swpackage requires the
fileset and tag keywords, plus zero or more file specifications.
You can define additional disk space requirements for the fileset using a
space control_file. (See the
Control Script Specification section for more information.)
fileset
Keyword that begins fileset specification.
tag Defines the identifier (short name) for the fileset.
architecture
Describes the target system(s) on which the fileset will run if filesets for multiple architecture
are included in a single product. Provides a human-readable summary of the four
uname
attributes which define the exact target system(s) the product supports. Many filesets do not
include an architecture; only a product architecture need be defined.
ancestor
A list of filesets that will match the current fileset when installed on a target system, if the
match_target installation option is specified. Also determines the base to which a patch is
applied.
category_tag
A repeatable tag-based attribute identifying a set of categories of which the software object is a
member. This is used as a selection mechanism and can be used independent of patches. The
default value is an empty list or patch if the is_patch attribute is set to true.
Like
vendor_tag, this attribute can be used as a pointer to a category object that contains
additional information about the category (for example, a one-line title definition and a
description of the category).
Note that the category tag
patch is reserved. When is_patch is set to true, a built-in
category_tag attribute of value patch is automatically included.
NOTE: You can only change the patch value by performing a swpackage operation or by
using swmodify to change the value of the is_patch attribute.
description
Defines the multi-paragraph description of the fileset; the value is either the text itself (within
double-quotes) or a pointer to the filename containing the text.
dynamic_module
A space-separated list of strings specifies the list of dynamic_modules (DLKMs) packaged into
the fileset. For 11.23 and newer releases, the dynamic modules themselves must be delivered
to /usr/conf/mod/. If the dynamic_module attribute is ommitted, no DLKMs may be
delivered in the fileset.
When a dynamic module is packaged, it is customary to include a call to the control_util
mod_systemfile in a postinstall script to link the module to the kernel. If a state of static is
specified in the mod_systemfile call, the attributes is_kernel and is_reboot must also be set to
true. In addition, if a system reboot is needed to activate the module, the is_reboot attribute
must be set to true.
is_kernel
A value of "true" defines the fileset as being a contributor to the operating system kernel; the
target system(s) kernel build process will be invoked after the fileset is installed. If this attri-
bute is not specified, swpackage assumes a default value of "false".
is_locatable
Defines whether the fileset can be installed into any directory, or whether it must be installed
into a specific directory. If this attribute is not specified, swpackage assigns a value of
true.
is_patch
Identifies a software object as a patch. The default value is false. When set to true,a
built-in category_tag attribute of value patch is automatically included.
HP-UX 11i Version 3: September 2010 − 15 − Hewlett-Packard Company 15