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

Postremove Performs additional remove operations (such as restoring “rollback” files)
immediately after a fileset or product has been removed. (Executed by
swremove.)
Preinstall Performs file operations (such as removing obsolete files) immediately before
installation of software files. (Executed by swinstall.)
Preremove Performs additional file operations (such as removing files created by a
preinstall script) immediately before removal of software files. (Executed by
swremove.)
Request Requests an interactive response from the user as part of the installation or
configuration process. (Executed by swask, swconfig, and swinstall.)
Unconfigure Undoes configurations performed by configure scripts. (Executed by
swconfig and swremove.)
Unpostinstall Undoes a postinstall script in case swinstall must initiate recovery during
the installation process. (Executed by swinstall.)
Unpreinstall An undo preinstall script in case SD must initiate recovery during the install
process. (Executed by swinstall.)
Verify Verifies the configuration of filesets or products in addition to the standard
swverify checks. (Executed by swverify.)
10.4 Creating a Product Specification File (PSF)
SD-UX uses a Product Specification File (PSF) to define the physical product package. The PSF
provides a “road map” that identifies the product according to its attributes, contents, compatibilities,
dependencies and descriptions. The PSF drives the swpackage session. It describes how the
product is structured and defines the attributes that apply to it.
SD-UX packages, distributes, installs files. The SD-UX packager uses these files after they have been
built and installed into specific directory locations. These directory locations may reside in separate,
unconnected directory trees or in the specific file locations needed to make the software run on
your system. You can specify files by a root directory (gathering all files below it) or by explicit
individual file paths. The file attributes can be taken from the files themselves, specified separately
for each file, or specified for a set of files.
The PSF can:
• Define vendor information (optional) for groups of products (including all products), or for
individual products.
• Specify one or more products (required).
• For each product, define attributes for one or more subproducts (optional), filesets (required),
and files (required).
• Define attributes for the distribution depot/media (optional).
• Specify what computer(s) and operating system(s) the product supports.
• Define attributes that describe the software objects.
10.4.1 Product Specification File Examples
10.4.1.1 Minimal PSF
Here is an example of the minimum PSF, which includes only the required keywords. This PSF
creates a product SD with fileset commands and contains one file, /usr/sbin/swcopy:
product
tag SD
fileset
10.4 Creating a Product Specification File (PSF) 173