Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

Table Of Contents
boolean
Maximum length: 9 bytes
One of the values true or false.
Examples: true, false
file_specification
Maximum length: none
Explicitly specifies a file or directory to be packaged, using
the format:
[-m mode] [-o [owner[,]] [uid]] [-g [group[,]][gid]]
[-v][source] [destination]
The source and destination can be paths relative to source
and destination directories specified in the
path_mapping_string.
You can also use * to include all files below the source
directory specified by a directory keyword.
Examples: -m 04555 sbin/swinstall or * (to denote
all files and directories)
multi_line_string
Maximum length: 8 kbyte (1Mbyte for a readme file)
Each multi-line strings support all isascii characters.
(Refer to the ctype(3) manpage.) It represent one or more
paragraphs of text. It can be specified in-line, surrounded
by double-quotes or read from a files.
File entries must use this syntax:
< filename
Example: </mfg/sd/description
one_line_string
Maximum length: 256 bytes
One-line strings support a subset of isascii characters
only. (Refer to the ctype(3) manpage.)
No isspace characters, except for space and tab, are
allowed.
Examples: Hewlett-Packard Company
path_mapping_string
Maximum length: none
A value of the form: source[=destination] where
the source defines the directory in which subsequently
defined files are located. The optional destination
maps the source to a destination directory in which the
files will actually be installed.
Examples:/mfg/sd/files/usr = /usr
path_string
Maximum length: 255 bytes for tapes, 1024 bytes for
depots
An absolute or relative path to a file. Many attributes of
this type are restricted to 255 bytes in length. This
restriction is due to the tar(1) command, which requires a
file’s basename(1) be <= 100 bytes, and a file’s
dirname(1) to be <= 155 bytes. (Some implementations
of tar enforce < and not <=.)
Creating a Product Specification File (PSF) 173