Software Distributor Administrator Guide (September 2010)

corequisite P.F
prerequisite ProdA | ProdB | ProdC.F | ProdC.FS
corequisite ProdX | ProdY | ProdZ | ProdW.FS
10.4.2.4.10 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. You can write the scripts and
include them in your software package. All scripts are optional but often are needed
correctly complete the task that you want your software package to perform. See
Chapter 11: “Using Control Scripts ” (page 269) for a complete discussion of control
scripts.
10.4.2.4.11 File Specification
Within a fileset specification, you can specify the following file types to be packaged
into the fileset by swpackage:
• control script
• directory
• hard link
• regular file
• symbolic link
• archive
swpackage generates an error if the PSF contains an unrecognized or unpackageable
file type.
The swpackage command supports specific mechanisms for specifying the files
contained in a fileset:
default permission specification For all or some of the files in the fileset, you can
define a default set of permissions.
directory mapping
You can point swpackage at a source directory
in which the fileset’s files are located. In addition,
you can map this source directory to the
appropriate (destination) directory in which this
subset of the product’s files will be located.
explicit file specification For all or some of the files in the fileset, you can
name each source file and destination location.
recursive (implicit) file
specification
If directory mapping is active, you can simply
tell swpackage to recursively include all files in
the directory into the fileset.
PSF extensions You can use include and exclude files to extend
file definitions.
246 Creating Software Packages