HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
s
swpackage(1M) swpackage(1M)
NAME
swpackage - package software products into a target depot or tape
SYNOPSIS
swpackage [-p][-v][-V][-C session_file ][-d directory|device ][-f software_file]
[-s product_specification_file|directory ][-S session_file ][-x option=value ][-X option_file]
[software_selections][@ target_selection]
Remarks
• For a description of the Product Specification File (PSF) used as input to the swpackage command,
see the swpackage(4) man page by typing man 4 swpackage on the command line.
• For an overview of all SD commands, see the sd(5) man page by typing man 5 sd on the command
line.
• For descriptions of all SD objects, attributes and data formats, see the sd(4) man page by typing man 4
sd
on the command line.
DESCRIPTION
The swpackage command is not distributed; it only operates on the local host. It packages software pro-
ducts 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 sub-
set the filesets into logical groupings. (Subproducts are optional.) A product, subproduct, and fileset also
have attributes associated with them.
Both directory and tape distributions use the same format. The
swpackage command:
• Organizes the software to be packaged into products, subproducts, and filesets,
• Provides flexible mechanisms to package source files into filesets,
• Modifies existing products in a distribution directory,
• Copies products in a distribution directory to a distribution tape.
Both the
swpackage and swcopy commands create or modify a target depot. The differences between
these commands are:
• The swcopy command copies products from an existing depot to another depot. The swpack-
age
command creates products based on the user’s specification, and packages these products into a
depot.
• swpackage can be used to re-package software_selections from an existing distribution directory
to a distribution tape.
• The swcopy command can copy from a local or remote source to a set of local or remote targets.
The swpackage command packages source files from the local filesystem into a product, for inser-
tion into a local distribution directory or tape.
• After creating a target depot, swcopy registers that directory with the local swagentd so that it
can be found by
swlist, swinstall , etc. With swpackage, the depot is not registered; the
user must explicitly invoke the swreg command.
Layout Version
By default, SD object and attribute syntax conforms to the layout_version 1.0 specification of the IEEE
POSIX 1387.2 Software Administration standard. SD commands still accept the keyword names associated
with the older layout version 0.8, but you should use the older version only to create distributions readable
by older versions of SD.
Which
layout_version the SD commands write is controlled by the layout_version
option or by
specifying the
layout_version attribute in the PSF file.
See sd(4), the description of the layout_version
option in the following section and in sd(5) for more
information. See sd(4) for more information on
PSF files.
Section 1M−−914 − 1 − HP-UX Release 11i: December 2000
___
___