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

[-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. The
mode and umask are unsigned integers, but only supports
the octal character set, 0-7.
• SD-UX will not override existing permissions based on this
attribute if a file already exists on a target.
• Examples: -u 0222 -o root -g sys
revision_string
Maximum length: 64 bytes•
• Revision strings contain zero or more dot-separated
one_line_string (above).
• Examples: 2.0, B.11.00
software_specification
Maximum length: none•
• Software specifications are used to specify software in
dependencies, ancestors and other attributes, as well as
command line selections. This attribute uses the standard
syntax for SD-UX software_selections. See “Software
Selections” (page 35) for complete information.
• Examples: SD.agent or
SD,r=2.0,a=HP-UX_B.11.00_32
tag_string
Maximum length: 64 bytes•
• Tag strings support a subset of isascii characters only:
Requires one or more characters from: “A-Z”, “a-z”,
“0-9”, including the first character.
◦
◦ The isspace characters are not allowed.
◦ SDU metacharacters not allowed: . , : =
◦ Shell metacharacters not allowed: # ; & () {} |
< >
◦ Shell quoting characters not allowed: “ ‘ ’ \
◦ Directory path character (/) not allowed.
• Examples: HP, SD-UX
uname_string
Maximum length: 64 bytes•
• Uname strings containing a subset of isascii() characters
only.
• No isspace() characters are allowed.
• Shell pattern matching notation allowed: [ ] * ? !
• Patterns can be “ORed” together using the separator: |
• Examples: 9000/7*:*|9000/8*:*, HP-UX, ?.11.*
180 Creating Software Packages