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

corequisites SD.data
corequisites SD.agent
# Control files:
configure scripts/configure.commands
# Files:
directory ./commands=/usr/sbin
file swinstall
file swcopy
# (...Other file definitions can go here...)
directory ./nls=/usr/lib/nls/C
file swinstall.cat
file swpackage.cat
directory ./ui=/var/adm/sw/ui
file *
# (...Other file definitions can go here...)
end
# Commands
# (...Other fileset definitions can go here...)
# Manpage fileset definitions:
fileset
tag man
title Manual pages for the SD-UX
revision 2.05
directory ./man/man1m=/usr/man/man1m.Z
file *
directory ./man/man4=/usr/man/man4.Z
file *
directory ./man/man5=/usr/man/man5.Z
file *
end
#man
end
#SD
10.4.2 PSF Syntax
Each SD-UX object (product, subproduct, filesets, and file) has its own set of attributes and each
attribute has a keyword that defines it. Most attributes are optional; they do not all need to be
specified in the PSF. Each attribute has its own specific requirements, but the following rules apply:
• Keyword syntax is:
keyword value
• All keywords require one or more values, except as noted. If the keyword is there but the value
is missing, a warning message is generated and the keyword is ignored.
• Place comments on a line by themselves or after the keyword-value syntax. Comment lines
are designated by preceding them with #.
• Use quotes when defining a value (for example, description) that can span multiple lines.
Quotes are not required when defining a single-line value that contains embedded whitespace.
• Any errors encountered while reading the PSF cause swpackage to terminate. Errors are also
logged to both stderr and the logfile.
10.4.2.1 PSF Object Syntax
The following tables and sections describe the PSF keywords, the allowable values for each keyword,
and the syntax for the objects you can define in a PSF.
10.4 Creating a Product Specification File (PSF) 175