set characteristics file
file that describes the characteristics of the set along with
information that helps control the flow of installation.
It is created by the software set developer and is included
in the Set Installation Package (SIP).
A SIP is a special purpose package that controls the installation
and removal of a set of packages.
Each entry in the setinfo file
is a line that consists of predefined fields.
Each entry corresponds to a package belonging to the set and
must contain the following <tab>-separated fields:
1. Package Abbr
This field contains the abbreviated name of the package.
must be a short string (no more than nine characters long) and must conform
to the file naming rules.
All characters in the abbreviation must be
alphanumeric and the first character cannot be numeric.
new, and all are reserved.
This abbreviated name must be the same as the one used in
This field specifies the number of parts
this package consists of.
This field contains the character 'y' indicating that the
package is to be installed as a default.
Conversely, an 'n' indicates that the
package will not be installed.
The category under which the package belongs.
Four categories are defined:
``application,'' ``graphics,'' ``system'' and ``utilities.''
All packages must be assigned to one of these
If you choose, you can also assign a package to a category
Categories are case-insensitive and may contain only
Each category is limited to 16 characters.
5. Package Full-Name
Text that specifies the package name (maximum length of 256 ASCII
This field must be the same as NAME in
Differences between versions
This file is part of the UnixWare packaging tools
that are supported only on SCO OpenServer Release 5.0.5a and later releases.
setinfo file for set admin:
#ident "@(#)set:cmn/set/admin/setinfo 1.2"
#ident "$Header: $"
# Format for the setinfo file. Field separator is: <tab>
# pkg parts default category pkg full-name
# abbr y/n
oam 4 y application OA&M
bkrs 1 y system Extended Backup and Restore
face 1 y application FACE
The order of the packages listed in the setinfo file
must reflect any package dependencies
and must represent the order
in which the packages will occur on the media
(in the case of datastream).
Any package for which there exists a dependency
must be listed prior to the package(s) that depends on it.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005