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

The following examples illustrate the use of the file_permission keyword.
• Set a read only 444 mode for all file objects (requires override for every executable file and
directory):
file_permissions -m 444
• Set a read mode for non-executable files, and a read/execute mode for executable files and
directories:
file_permissions -u 222
• Set the same mode defaults, plus an owner and group:
file_permissions -u 222 -o bin -g bin
• Set the same mode defaults, plus a uid and gid:
file_permissions -u 222 -o 2 -g 2
• Set the owner write permission in addition to the above:
file_permissions -u 022 -o 2 -g 2
• If you do not define file_permissions, swpackage uses the default value
file_permissions -u 000 for destination file objects based on existing source files.
(Meaning the mode, owner/uid, group/gid are set based on the source file, unless specific
overrides are specified for a destination file.)
10.4.2.4.11.2 Directory Mapping
(Optional) The directory source [= destination] specification defines the source directory
under which subsequently listed files are located. In addition, you can map the source directory
to a destination directory under which the packaged files will be installed.
For example, the definition:
directory /build/hpux/mfg/usr = /usr
causes files from the /build/hpux/mfg/ directory to have the prefix /usr/sbin when installed.
The destination directory must be a superset of the product’s directory attribute, if defined in
the product specification. If the product’s directory is defined, and the destination is not a
superset, swpackage generates an error.
The destination directory must be an absolute pathname. If not, then swpackage generates an
error.
The source directory can either be an absolute pathname, or a relative pathname. If relative,
swpackage interprets it relative to the current working directory in which the command was
invoked.
If the source directory does not exist, swpackage generates an error.
10.4.2.4.11.3 Explicit File Specification
You can explicitly specify the files to be packaged into a fileset. If you want to recursively include
all files and directories, use the recursive file specification (file *).
You can use the directory keyword to define a source (and destination) for explicitly specified
files. If no directory keyword is active, then the full source path and the absolute destination
path must be specified for each file. An explicit file specification overrides or adds to, on a file-by-file
basis, the specifications set by the directory and/or file_permissions keywords.
An explicit file specification uses this form:
file [-v] [-m mode] [-o [owner[,]][uid]] [-g [group[,]][gid]]
[-t type] [source] [destination]
10.4 Creating a Product Specification File (PSF) 191