swpackage.4 (2010 09)

s
swpackage(4) swpackage(4)
Examples: /mfg/sd/files/usr = /usr
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.
file_specification
Maximum length: none
Examples:
-m 04555 sbin/swinstall
or * (to denote all files and directories)
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
direc-
tory keyword.
permission_string
Maximum length: none
Examples: -u 0222 -o root -g sys
A value of the form:
[-m mode|-u umask ][-o [owner[,]][uid]]
[-g [group[,]][gid]]
where each component defines a default permissions value for each file and directory
defined in a fileset. The default values can be overridden in each file’s specific definition.
The owner and group fields are of type tag_string. The uid and gid fields are of type
unsigned integer. To specify a numeric username on systems that support numeric user-
names for owners, you must specify both the numeric owner username and the uid. Simi-
larly, to specify a numeric groupname, you must specify both the numeric group group-
name and the gid. If only one value is supplied for owner/group, it will be interpreted as
an id if the value is numeric. Otherwise, it will be interpreted as a name. The mode and
umask are unsigned integers, but only supports the octal character set: "0"-"7".
software_specification
Maximum length: none
Examples: SD.agent or SD,r=2.0,a=HP-UX_B.11.23_IA/PA
Software specifications are used to specify software in dependencies, ancestors and other
attributes, as well as command line selections. The SD commands and attributes support
the following syntax for each software_specification:
bundle
[.product[.subproduct][.fileset]][,version]
product[.subproduct][.fileset][,version]
• You can specify selections with the following shell wildcard and pattern-matching
notations:
[], *, ?
For example, *man selects all bundles and products with tags that end with "man".
• Bundles and subproducts are recursive. Bundles can contain other bundles and sub-
products can contain other subproducts , for example:
bun1.bun2.prod.sub1.sub2.fset,r=1.0
or (using expressions):
bun[12].bun?.prod.sub*,a=HP-UX
• The \* software specification selects all products. Use this specification with cau-
tion.
The version component has the form:
[,r <op> revision][,a <op> arch][,v <op> vendor]
[,c <op> category][,q=qualifier][,l=location]
HP-UX 11i Version 3: September 2010 − 7 − Hewlett-Packard Company 7