HP-UX Reference (11i v1 00/12) - 4 File Formats (vol 8)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man4/!!!intro.4
________________________________________________________________
___ ___
s
swpackage(4) swpackage(4)
(Hewlett-Packard Company)
Keyword Type Size Example
checkinstall path_string 1024 ./scripts/checkinstall
checkremove path_string 1024 ./scripts/checkremove
configure path_string 1024 ./scripts/configure
control_file path_string 1024 ./scripts/subscripts
postinstall path_string 1024 ./scripts/postinstall
postremove path_string 1024 ./scripts/postremove
preinstall path_string 1024 ./scripts/preinstall
preremove path_string 1024 ./scripts/preremove
request path_string 1024 ./scripts/request
unconfigure path_string 1024 ./scripts/unconfigure
unpreinstall path_string 1024 ./scripts/unpreinstall
unpostinstall path_string 1024 ./scripts/unpostinstall
verify path_string 1024 ./scripts/verify
Vendor-Defined Attributes
You can create your own software attributes when packaging software. Keywords in a product specification
file that are not recognized by SD are preserved, along with their associated values, by being transferred to
the resulting INDEX or INFO files created by swpackageor swcopy. (Refer to swpackage(4) for more
information on INDEX and INFO files.)
The keyword is a filename character string. The value associated with a keyword is processed as an
attribute_value. It can be continued across multiple input lines or can reference a file containing the value
for the keyword.
Vendor-defined attributes are noted during packaging or when modified with
swmodify. These attributes
can be listed with
swlist.
As always, use caution in constructing your Product Specification File. If you misspell a standard keyword,
SD may mistake the keyword for a vendor-defined attribute.
VALUE TYPES
The value for each attribute must be of a specific type. The types are:
tag_string
Maximum length: 64 bytes
Examples: HP, SD
Tag strings support a subset of isascii() characters only:
Requires one or more characters from: "A-Z", "a-z", "0-9", includingthe 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: /
one_line_string
Maximum length: 256 bytes
Examples: Hewlett-Packard Company
One-line strings support a subset of isascii() characters only:
No isspace() characters, except for space and tab, are allowed.
multi_line_string
Maximum length: 8K (1Mb for readme)
Multi-line strings support all isascii() characters. They represent one or more para-
graphs of text. They can be specified in-line, surrounded by double-quotes. They can also
be stored in a file, and specified using the ‘‘< filename’’ format.
revision_string
Maximum length: 64 bytes
Examples: 2.0, B.11.00
Revision strings contain zero or more dot-separated one_line_strings (above).
HP-UX Release 11i: December 2000 − 6 − Section 4−−291
___
___