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)
targets option contains a list of software_collection_specs for all targets specified for the com-
mand. When the file pointed to by SW_SESSIONS_OPTIONS is made available to other
scripts, the targets option contains the single software_collection_spec for the targets on which
the script is being executed.
SW_SOFTWARE_SPEC
This variable contains the fully qualified software specification of the current product or fileset.
The software specification allows the product or fileset to be uniquely identified.
File Specification
Within a fileset specification, the user can specify the following file types to be packaged into the fileset by
swpackage:
control file
directory
hard link
regular file
symbolic link
An error results if you specify a recognized but unpackageable type or an unrecognized type.
The swpackage command supports these mechanisms for specifying the files contained in a fileset:
Default permission specification
For some or all of the files and directories in the fileset, the user can define a default set of per-
missions.
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.
Explicit file specification
For some or all of the files and directories in the fileset, the user can name each source file and
destination location.
Recursive (implicit) file specification
If a directory mapping is active, the user can tell swpackage to include all files and directories
in the fileset (recursively) below the specified directory.
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
Section 4−−304 − 19 − HP-UX Release 11i: December 2000
___
___