swpackage(4) — SD 2.0 Release
NAME
swpackage − product specification file (PSF) format
DESCRIPTION
The swpackage command packages software products into:
• a distribution directory (which can be accessed directly, or copied onto a CD-ROM),
• a distribution tape (such as DDS, nine-track or cartridge tapes).
A software product is organized into a three-level hierarchy: products, subproducts, and filesets. The actual files that make up a product are packaged into filesets. Subproducts can be used to partition or subset the filesets into logical groupings. (Subproducts are optional.) A product, subproduct, and fileset also have attributes associated with them (described below).
Both directory and tape distributions use the same format. See sd(4) for details on this format.
A Product Specification File (PSF) drives the swpackage session. It defines how a product is structured, and the attributes that apply to it. This manual page describes the syntax and semantics of a PSF.
PRODUCT SPECIFICATION FILE SYNTAX
A PSF is structured as follows:
[<depot specification>]
[<vendor specification>]
<product specification>
[<vendor specification>]
[<subproduct specifications>]
[<control script specifications>]
<fileset specification>
[<control script specifications>]
[<file specifications>]
[<fileset specification>]
...
[<product specification>]
...
In summary, the swpackage user can:
• Specify attributes for the target depot/tape (optional);
• Specify one or more products;
• Specify vendor information (optional) for groups of products (including all products), or for individual products.
• For each product, specify one or more subproducts (optional);
• For each product, specify one or more filesets.
• For each fileset, specify one or more files.
• For each product or fileset, specify one or more control scripts.
There are attributes associated with each object that the user can define. All objects and attributes are defined using a
keyword value
syntax. The keyword is an identifier for the attribute. Most attributes are optional. There are specific rules for each keyword, as described below. The following rules generally apply:
• All keywords require one or more values, except as noted. If the value is missing an error is given.
• Comments can be placed on a line by themselves or after the keyword-value syntax. They are designated by preceding them with #.
• The use of double quotes ("") is required when defining a value (e.g. description ) which spans multiple lines.
• The use of double quotes (") is not required when defining a value that contains embedded whitespace. The quotes can be used, however.
Attribute Table
The following tables summarize the objects and attributes which can be defined in a PSF.
| Keyword | Type | Size | Example |
| depot | |||
| tag | tag_string | 16 | APPLICATIONS_CD |
| title | one_line_string | 80 | HP-UX Applications Software Disc |
| description | multi_line_string | 2048 | < data/description.cd |
| copyright | multi_line_string | 8192 | < data/copyright.cd |
| number | tag_string | 32 | B2358-13601 |
| end | |||
| vendor | |||
| tag* | tag_string | 16 | HP |
| uuid* | hex_string | 40 | 1234567-CDEF-0123-4569ABCDEF |
| title | one_line_string | 80 | Hewlett-Packard Company |
| description | multi_line_string | 2048 | < data/description.hp |
| end | |||
| product | |||
| tag* | tag_string | 16 | SD |
| revision* | revision_string | 32 | 2.0 |
| title | one_line_string | 80 | HP OpenView Software Distributor |
| description | multi_line_string | 2048 | < data/description.sd |
| copyright | multi_line_string | 8192 | < data/copyright.sd |
| readme | multi_line_string | 1024K | < data/README.sd |
| number | tag_string | 32 | J2326AA |
| category | one_line_string | 80 | systems management |
| directory | path_string | 1024 | / |
| is_locatable | boolean | 5 | false |
| architecture* | one_line_string* | 80 | S700/S800_HP-UX_9.0 |
| machine_type | uname_string | 64 | 9000/7*|9000/8* |
| os_name | uname_string | 32 | HP-UX |
| os_release | uname_string | 32 | ?.09.* |
| os_version | uname_string | 32 | [A-Z] |
| end |
The attributes marked with a * determine the uniqueness of a product definition. Their values are also of type version_component, in addition to the defined type above.
Attribute Table (continued)
| Keyword | Type | Size | Example |
| subproduct | |||
| tag | tag_string | 16 | Manager |
| title | one_line_string | 80 | Management Utilities |
| description | multi_line_string | 2048 | < data/description.manager |
| contents | one-line list of | commands agent data man | |
| tag_string values | |||
| end | |||
| fileset | |||
| tag | tag_string | 16 | commands |
| revision | revision_string | 32 | 2.15 |
| title | one_line_string | 80 | Commands (management utilities) |
| description | multi_line_string | 2048 | < data/description.commands |
| is_kernel | boolean | 5 | false |
| is_reboot | boolean | 5 | false |
| prerequisite | software_specification | SD.agent | |
| corequisite | software_specification | SD.man | |
| directory | path_mapping_string | ./commands = /usr/sbin | |
| file | all_files_directive | * | |
| file | file_specification | -m 04555 sbin/swinstall | |
| file_permissions | permission_string | -u 0222 -o root -g sys | |
| end | |||
| (control scripts) | |||
| checkinstall | path_string | 1024 | ./scripts/checkinstall |
| preinstall | path_string | 1024 | ./scripts/preinstall |
| postinstall | path_string | 1024 | ./scripts/postinstall |
| configure | path_string | 1024 | ./scripts/postinstall |
| unconfigure | path_string | 1024 | ./scripts/postinstall |
| verify | path_string | 1024 | ./scripts/postinstall |
| checkremove | path_string | 1024 | ./scripts/postinstall |
| preremove | path_string | 1024 | ./scripts/postinstall |
| postremove | path_string | 1024 | ./scripts/postinstall |
| control_file | path_string | 1024 | ./scripts/subscripts |
Control scripts can be defined for filesets and/or products.
Value Types
The value for each attribute must be of a specific type (as noted in the table above). The types are:
tag_string
maximum length: 16 bytes
examples: HP, SD
Tag strings support a subset of isascii(3) characters only:
Requires one or more characters from: "A-Z", "a-z", "0-9", including the first character.
The isspace(3) characters are not allowed.
SDU metacharacters not allowed: .,=#
Shell metacharacters not allowed: ;&(){}|<>
Shell quoting characters not allowed: "‘’\
Directory path character not allowed: /
hex_string
maximimum length: 40 bytes
examples: 01234567-CDEF-0123-4569ABCDEF
Uuids composed of 32 hexadecimal digits separated by dashes.
Represents an unsigned integer. (Each hex digit represents 4 bits of the unsigned integer.)
Allows hexadecimal digits: 0-9, A-F
Allows separator characters: -
one_line_string
maximum length: 80 bytes
examples: Hewlett-Packard Company
One-line strings support a subset of isascii(3) characters only:
No isspace(3) characters, except for space and tab, are allowed.
multi_line_string
maximum length: 2048, 8192, or 1024K bytes
Multi-line strings support all isascii(3) characters. They represent one or more paragraphs 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: 32 bytes
examples: 2.0, A.09.00
Revision strings contain zero or more dot-separated one_line_strings (above).
boolean
maximum length: 5 bytes
examples: true, false
One of the values "true" or "false".
path_string
maximum length: 255 bytes for tapes, 1024 bytes for depots
examples: /usr, /mfg/sd/scripts/configure
An absolute or relative path to a file.
uname_string
maximum length: 32 or 64 bytes
examples: 9000/7*|9000/8*, HP-UX, ?.09.*, [A-Z]
Uname strings containing a subset of isascii(3) characters only.
No isspace(3) characters are allowed.
Shell pattern matching notation allowed: []*?!
Patterns can be "or’ed" together using the separator: |
path_mapping_string
maximum length: none
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.
all_files_directive
maximum length: 1 byte
examples: *
Directs swpackage to include all files below the source directory specified in the path_mapping_string.
file_specification
maximum length: none
examples: -m 04555 sbin/swinstall
Explicitly specifies a file to be packaged, using the format:
[-m mode] [-o [owner[,]][uid]] [-g [group[,]][gid]] [-v] .br [source] [destination]
The source and destination can be paths relative to source and destination directories specified in the path_mapping_string.
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 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".
software_specification
maximum length: none
examples: SD.agent, SD,r=2.0,a=Series_700/800_HP-UX_9.0,v=HP
An SD software specification of the form:
product[.subproduct][.fileset][,version]
where the version component has the form:
[r=revision][,a=arch][,v=vendor][,vid=vendor_uuid]
version_component
maximum length: none
A further restriction for the tag, revision, architecture, vendor tag, and vendor uuid, attributes.
No isspace(3) characters are allowed.
Shell pattern matching notation not allowed: []*?!
PRODUCT SPECIFICATION FILE SEMANTICS
The following sections describe the attributes which can be defined.
Depot (Tape) Specification
depot
tag APPLICATIONS_CD
title HP-UX Applications Software Disc
description < data/description.cd
copyright < data/copyright.cd
number B2358-13601
[<vendor specification>]
<product specification>
[<product specification>]
...
end
Each keyword defines an attribute of the distribution depot (tape) itself.
depot
If a depot specification is included in the PSF, swpackage requires only the depot keyword, plus one or more contained product definitions.
tag Defines the identifier (short name) for the distribution depot/tape.
title
Defines the full name (one-line description) of the distribution depot/tape.
description
Defines the multi-paragraph description of the distribution depot/tape; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
copyright
Defines the copyright information for the distribution depot/tape; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
number
Defines the part or manufacturing number of the distribution depot (e.g. CD-ROM) or tape.
end Ends the depot specification. This keyword is optional.
Vendor Specification
vendor
tag HP
uuid 01234567-CDEF-0123-4569ABCDEF
title Hewlett-Packard Company
description < data/description.hp
end
Each keyword defines an attribute of a vendor object.
vendor
If a vendor specification is included in the PSF, swpackage requires the vendor and tag keywords.
tag Defines the identifier (short name) for the vendor.
uuid Defines the vendor’s NetLS Universal Unique Indentifier (UUID). (This attribute is only useful for vendors who license their software using NetLS.)
title
Defines the full name (one-line description) for the vendor.
description
Defines the multi-paragraph description of the vendor; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
end Ends the vendor specification. This keyword is optional.
Product Specification
product
tag SD
revision 2.0
title HP OpenView Software Distributor
description < data/description.sd
copyright < data/copyright.sd
readme < data/README.sd
number J2326AA
category systems management
directory /
is_locatable false
architecture S700/S800_HP-UX_9.0
machine_type 9000/7*|9000/8*
os_name HP-UX
os_release ?.09.*
os_version [A-Z]
[<vendor specification>]
[<subproduct specifications>]
[<control script specifications>]
<fileset specification>
[<fileset specification>]
...
end
Each keyword defines an attribute of a product object.
product
For each product specified, swpackage requires only the product and tag keywords, plus one or more contained fileset definitions.
tag Defines the identifier (short name) for the product.
revision
Defines the revision (release number, version number) of the product.
title
Defines the full name (one-line description) of the product.
description
Defines the multi-paragraph description of the product; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
copyright
Defines the copyright information for the product; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
readme
Defines the README information for the product; the value must be a pointer to the filename containing the text.
number
Defines the part or order number for the product.
category
Defines the term or phrase that categorizes the product (e.g. "systems management", "CASE", "database", etc.).
directory
Defines the default, absolute pathname to the directory in which the product’s files will be installed (i.e. the root directory of the product). If this attribute is not specified, swpackage assigns a value of "/".
is_locatable
Defines whether the product can be installed into any directory, or whether it must be installed into a specific directory. If this attribute is not specified, swpackage assigns a value of "false".
architecture
Describes the target system(s) on which the product will run. Provides a human-readable summary of the four uname(1) attributes which define the exact target system(s) the product supports.
machine_type
Defines the machine(s) on which the product will run. (If not specified, swpackage assigns a value of "*", meaning the product runs on all machines.) If there are multiple machine platforms, use wildcards or the ’|’ character to identify them. This attribute should pattern match to the value of uname -m on the supported target machine(s).
os_name
Defines the operating system(s) on which the product will run. (If not specified, swpackage assigns a value of "*", meaning the product runs on all operating systems.) If there are multiple operating systems, use wildcards or the ’|’ character to identify them. This attribute should pattern match to the value of uname -s on the supported target system(s).
os_release
Defines the operating system release(s) on which the product will run. (If not specified, swpackage assigns a value of "*", meaning the product runs on all releases.) If there are multiple operating system releases, use wildcards or the ’|’ character to identify them. This attribute should pattern match to the value of uname -r on the supported target system(s).
os_version
Defines the operating system version(s) on which the product will run. (If not specified, swpackage assigns a value of "*", meaning the product runs on all versions.) If there are multiple operating system versions, use wildcards or the ’|’ character to identify them. This attribute should pattern match to the value of uname -v on the supported target system(s).
end Ends the product specification. This keyword is optional.
Subproduct Specification
subproduct
tag Manager
title Management Utilities
description < data/description.manager
contents commands agent data man
end
Each keyword defines an attribute of a subproduct object.
subproduct
If a subproduct is specified, swpackage requires the subproduct, tag, and contents keywords.
tag Defines the identifier (short name) for the subproduct.
title
Defines the full name (one-line description) of the subproduct.
description
Defines the multi-paragraph description of the subproduct; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
contents
Defines the filesets that make up the subproduct. The value is a whitespace separated list of fileset tag values.
In the PSF, fileset definitions are not contained within subproduct definitions. The contents keyword is used to assign filesets to subproducts.
end Ends the subproduct specification. This keyword is optional.
Fileset Specification
fileset
tag commands
revision 2.15
title Commands (management utilities)
description < data/description.commands
is_kernel false
is_reboot false
[<control file specifications>]
[<dependency specifications>]
[<file specifications>]
end
Each keyword defines an attribute of a fileset object.
fileset
For each fileset specified, swpackage requires the fileset and tag keywords, plus zero or more file specifications.
tag Defines the identifier (short name) for the fileset.
revision
Defines the revision (release number, version number) of the fileset.
title
Defines the full name (one-line description) of the fileset.
description
Defines the multi-paragraph description of the fileset; the value is either the text itself (within double-quotes) or a pointer to the filename containing the text.
is_kernel
A value of "true" defines the fileset as being a contributor to the operating system kernel; the target system(s) kernel build process will be invoked after the fileset is installed. If this attribute is not specified, swpackage assumes a default value of "false".
is_reboot
A value of "true" declares that the fileset requires a system reboot after installation. If this attribute is not specified, swpackage assumes a default value of "false".
end Ends the fileset specification. This keyword is optional.
Dependency Specification
corequisite SD.data
...
prerequisite product,r=revision
...
Each keyword/value defines a dependency relationship on another software object. The object can be within the same product as the dependent fileset, or it can be (within) another product. Dependency specifications are optional. Multiple dependency specifications are allowed.
corequisite
Defines a run-time dependency on another software object. For this fileset to correctly operate, the other software must be installed and configured.
prerequisite
Defines an install-time dependency on another software object. For this fileset to be correctly installed (or configured), the other software must be installed (or configured).
Control Script Specification
checkinstall scripts/checkinstall
preinstall scripts/preinstall
postinstall scripts/postinstall
configure scripts/configure
unconfigure scripts/unconfigure
verify scripts/verify
checkremove scripts/checkremove
preremove scripts/preremove
postremove scripts/postremove
control_file scripts/subscripts [= tag]
Each script specification defines a control script object. The value of each keyword is the source filename for the control file.
Control files are optional. If present, swpackage will copy the specified source filename into the depot’s storage directory for the associated product or fileset.
checkinstall
Defines the installation check script executed by swinstall. This script is executed during the analysis of each target, and it checks that the installation can be attempted. If the check script returns 1 (ERROR), the product/fileset will not be installed.
preinstall
Defines the installation pre-load script executed by swinstall. This script is executed immediately before the product’s/fileset’s files are installed.
postinstall
Defines the installation post-load script executed by swinstall. This script is executed immediately after the product’s/fileset’s files are installed.
configure
Defines the configuration script executed by swinstall and swconfig. This script configures the target host for the product/fileset (and the product/fileset for the target host).
unconfigure
Defines the un-configuration script executed by swremove and swconfig. This script unconfigures the target host and the product/fileset, un-doing the configuration performed by the configure script.
verify
Defines the verification script executed by swverify. This script verifies the configuration performed by the configure script.
checkremove
Defines the remove check script executed by swremove. This script is executed during the analysis of each target, and it checks that the remove can be attempted. If the check script returns 1 (ERROR), the product/fileset will not be removed.
preremove
Defines the remove pre-remove script executed by swremove. This script is executed immediately before the product’s/fileset’s files are removed.
postremove
Defines the remove post-remove script executed by swremove. This script is executed immediately after the product’s/fileset’s files are removed.
control_file
Defines an arbitrary control file to be included with the product/fileset, and stored alongside the named control files. It is used to include a subscript called by the named scripts, or a data file read by these scripts. If the optional tag component of the value is not specified, swpackage uses the basename(1) of the source filename as the tag for the control file. (Otherwise, the tag value is used.)
File Specification
Within a fileset specification, the user can specify the following file types to be packaged into the fileset by swpackage:
control file
regular file
directory
hard link
symbolic link
If a recognized, unpackagable type or an unrecognized type is specified, an error is issued.
The swpackage command supports these mechanisms for specifying the files contained in a fileset:
Directory mapping
The user can point swpackage at a source directory in which the fileset’s files are located. In addition, the user can map this source directory to the appropriate (destination) directory in which this subset of the product’s files will be located.
Recursive (implicit) file specification
If a directory mapping is active, the user can tell swpackage to include all files (recursively) from within the directory in the fileset.
Explicit file specification
For some or all of the files in the fileset, the user can name each source file and destination location.
Default permission specification
For some or all of the files in the fileset, the user can define a default set of permissions.
These mechanisms can all be used in combination with the others.
Directory Mapping
The
directory source [= destination]
keyword defines a source directory under which subsequently listed files are located. In addition, the user can map the source directory to a destination directory under which the packaged files will be installed. For example, the definition:
directory ./commands = /usr/sbin
causes all files from the ./commands directory to have the prefix /usr/sbin when installed. The destination directory must be a located within the product.directory attribute, if defined. (This attribute is defined by the directory keyword in the product specification.)
The destination directory must be an absolute pathname.
The directory keyword is optional.
Recursive File Specification
The
file *
keyword directs swpackage to recursively include every file (and directory) within the current source directory in the fileset. (Partial wildcarding is not supported -- e.g. file dm* to indicate all files starting with "dm".)
The directory keyword must have been previously specified before the file * specification can be used.
All attributes for the destination file object are taken from the source file, unless a file_permissions keyword is active (this keyword is described below).
The user can specify multiple
directory source [= destination]
file *
pairs to gather files from different source directories into a single fileset.
Explicit File Specification
Instead of, or in addition to, the recursive file specification, the user can explicitly specify the files to be packaged into a fileset.
The user can use the directory keyword to define a source (and destination) for explicitly specified files. If no directory keyword is active, then the source path and the absolute destination path must be specified for each file.
An explicit file specification uses this form:
file [-m mode] [-o [owner[,]][uid]] [-g [group[,]][gid]] [-v] \ [source] [destination]
file Specifies an existing file (perhaps within the currently active source directory) to include in the fileset.
source
Defines the relative or absolute path to the source file.
If this is a relative path, swpackage will search for it relative to the source directory set by the directory keyword. If no source directory is active, swpackage will search for it relative to the current working directory in which the command was invoked.
All attributes for the destination file object are taken from the source file, unless a file_permissions keyword is active, or the -m , -o , or -g , options are also included in the file specification.
destination
Defines the destination path at which the file will be installed. If destination is a relative path, the active destination directory set by the directory keyword will be prefixed to it. If it is a relative path, and no destination directory is active, swpackage generates an error. If the destination is not specified, then the source is used as the destination, with the appropriate mapping done with the active destination directory (if any).
-m mode
Defines the (octal) mode of a file or directory.
-o [owner[,]][uid]
Defines the destination file’s owner name and/or or uid. If only the owner is specified, then the owner and uid attributes are set for the destination file object, based on the packaging host’s /etc/passwd . If only the uid is specified, it is set as the uid attribute for the destination object and no owner name is assigned. If both are specified, each sets the corresponding attribute for the file object.
During an installation, the owner attribute is used to set the owner name and UID, unless the owner name is not defined in the target system’s /etc/passwd . In this case, the uid attribute is used to set the UID.
-g [group[,]][gid]
Defines the destination file’s group name and/or or gid. If only the group is specified, then the group and gid attributes are set for the destination file object, based on the packaging host’s /etc/group . If only the group is specified, and it contains digits only, it is interpreted as the gid, and is set as the gid attribute for the destination object; no group name is assigned to the object. If both are specified, each sets the corresponding attribute for the file object.
During an installation, the group attribute is used to set the group name and GID, unless the group name is not defined in the target system’s /etc/group . In this case, the gid attribute is used to set the GID.
-v Marks the file as volatile, meaning it can be modified (i.e. deleted) after installed without impacting the fileset.
When processing existing files in a source directory, a number of problems may be encountered. Errors messages are printed for each problem, and the file is not included in the fileset.
Example File Specifications
The following examples illustrate the use of the directory and file keywords:
Include all files under ./commands/, to be rooted under /usr/sbin/:
directory ./commands=/usr/sbin
file *
Include only certain files under ./commands/ and ./nls, to be rooted under /usr/sbin/ and /var/lib/nls/C/:
directory ./commands=/usr/sbin
file sbin/swinstall
file sbin/swcopy
...
directory ./nls=/usr/lib/nls/C/
file swinstall.cat
file swremove.cat
...
Explicitly list files, no directory mapping specified:
file ./commands/swinstall /usr/sbin/swinstall
...
file ./nls/swinstall.cat /usr/lib/nls/C/swinstall.cat
Use all specification types to include files:
directory ./commands=/usr/sbin
file *
directory ./nls=/usr/lib/nls/C
file swinstall.cat
...
file ./obam/obam.dm /etc/interface.lib/obam/obam.dm
Default Permission Specification
By default, a destination file object will inherit the mode, owner, and group of the source file. The file_permissions keyword can be specified to set a default permission umask/mode, owner, and group for all the files being packaged into the fileset:
file_permissions [-m mode|-u umask] [-o[owner[,]][uid]] \ [-g[group[,]][gid]]
file_permissions
Applies only to the fileset it is defined in. Multiple file_permissions can be specified, later definitions simply replace previous definitions.
-m mode
Defines a default (octal) mode for all file objects.
-u umask
Instead of specifying an octal mode as the default, the user can specify an octal umask (1) value which gets "subtracted" from an existing source file’s mode to generate the mode of the destination file.
By specifying a umask , the user can set a default mode for executable files, non-executable files, and directories. (A specific mode can be set for any file, as described above.)
-o[owner[,]][uid]
Defines the destination file’s owner name and/or or uid (as defined above).
-g[group[,]][gid]
Defines the destination file’s group name and/or or gid (as defined above).
Example Permission Specifications
The following examples illustrate the use of the file_permission keyword.
Set a readonly 444 mode for all file objects (requires override for every executable file and directory):
file_permissions -m 444
Set a read mode for non-executable files, and a read/execute mode for executable files and for directories:
file_permissions -u 222
Set the same mode defaults, plus an owner and group:
file_permissions -u 222 -o bin -g bin
Set the same mode defaults, plus a uid and gid:
file_permissions -u 222 -o 2 -g 2
Set the owner write permission in addition to the above:
file_permissions -u 022 -o 2 -g 2
If the user defines no file_permissions, swpackage uses the default value:
file_permissions -u 000
for destination file objects based on existing source files. (Meaning the mode, owner/uid, group/gid are set based on the source file, unless specific overrides are specified for a destination file.)
EXAMPLES
This example illustrates a product specification file for a product that defines all attributes.
# PSF file which defines an example packaging of the SD 2.0 product.
# Vendor definition:
vendor
tag HP
title Hewlett-Packard Company
description < data/description.hp
end
# Product definition:
product
tag SD
title HP OpenView Software Distributor
revision 2.0
number J2326AA
category Systems Management
description < data/description
copyright < data/copyright
readme < data/README
architecture S700/S800_HPUX_9.0
machine_type 9000/[78]*
os_name HP-UX
os_release ?.09.*
os_version ?
directory /
is_locatable false
# Create a product script which executes during the swremove
# analysis phase. (This particular script returns an ERROR,
# which prevents the removal of the SD product.)
checkremove scripts/checkremove.sd
# Subproduct definitions:
subproduct
tag Manager
title Management Utilities
contents commands agent data man
end
subproduct
tag Agent
title Agent component
contents agent data man
end
# Fileset definitions:
fileset
tag commands
title Commands (management utilities)
revision 2.15
description < data/commands
# Control scripts:
configure scripts/configure.commands
# Dependencies
corequisite SD.data
# Files:
directory ./commands=/usr/sbin
file swinstall
file swcopy
...
directory ./nls=/usr/lib/nls/C
file swinstall.cat
file swpackage.cat
file swutil.cat
directory ./ui=/var/adm/sw/ui
file *
...
end # commands
... # other filesets
fileset
tag man
title Manual pages for the Software Distributor
revision 2.05
directory ./man/man8=/usr/man/man8
file *
directory ./man/man4=/usr/man/man4
file *
directory ./man/man5=/usr/man/man5
file *
end # man
end # SD
AUTHOR
swpackage was developed by the Hewlett-Packard Company.
SEE ALSO
swpackage(8), sd(4), sd(5), and the HP OpenView Software Distributor Administrator’s Guide.
Hewlett-Packard Company — Software Distributor 2.0