Software Distributor Administration Guide for HP-UX 11i

Creating Software Packages
Creating a Product Specification File (PSF)
Chapter 10330
Control Script Specification SD-UX supports execution of product
and fileset control scripts that allow you to perform additional checks
and operations with other HP-UX commands and functions. The swask,
swinstall, swconfig, swverify, and swremove commands each can execute
one or more control scripts on the primary roots. All scripts are optional
but many times are needed correctly complete the task that you want
your software package to perform. See Chapter 11, “Using Control
Scripts,” on page 369 for a complete discussion of control scripts.
Subproduct Specification The subproduct specification lets you
group filesets within a larger product specification. Subproducts are
optional. A subproduct specification looks like this:
subproduct
tag Manager
contents manager agent packager man doc
description </mfg/sd/data/manager/description
title SD Management Interfaces Subset
end
Each keyword defines an attribute of a subproduct object. If a subproduct
object is specified, swpackage requires the subproduct, tag, and
contents keywords.
subproduct Keyword that begins a subproduct specification.
tag The subproduct’s identifier (short name).
contents A whitespace-separated list of the subproduct’s fileset
tag values (that is, contents
fileset1 fileset2
fileset3 ...filesetN
).
In the PSF, fileset definitions are not contained within
subproduct definitions. The contents keyword is used
to assign filesets to subproducts. This linkage allows a
fileset to be contained in multiple subproducts.
description A multi-line description of the subproduct; either the
text itself (within double-quotes), or a pointer to the
filename that contains the text.
title A one-line string that further identifies the subproduct.
end Ends the subproduct specification. No value is
required. This keyword is optional. If you use it and it
is incorrectly placed, the specification will fail.