Software Distributor Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (5900-2488, September 2012)

This also works well for permissions. For example, assume that nearly all the 100 files in the
preceding example had the same permission attributes, but files 1, 2, and 3 required a different
owner and mode:
directory source = /product
file_permissions -o bin -g bin -m 555
file *
file_permissions -o root -g other -m -04555
file 1
file 2
file 3
This capability combines the recursive file specifications function with explicit file specification.
(See “Explicit File Specification ” (page 191)).
10.5 Packaging the Software (swpackage)
The swpackage command packages software products defined in a PSF into a depot. You can
then use the software in the depot with other SD-UX commands.
Overview
Features and limitations include:
• Uses the PSF to organize files into products, subproducts, and filesets.
• Can include control scripts and PSFs to further specify how to handle the software when
installing it onto the target system.
• Sets permissions of the files being packaged.
• Can package either simple, one-fileset products or complex products with many filesets and
subproducts.
• Provides a way to repackage (change) existing products.
• The swpackage command provides only a command line user interface. There is no Graphical
User Interface for the packaging tasks.
• Can create directory depots (including CDs) or tape depots (useful for distributing software
via the internet).
• Does not automatically register newly created depots. You must use the swreg command (see
“Registering and Unregistering Depots (swreg) ” (page 95)).
The swpackage Process
The swpackage process includes up to four phases:
Table 47 swpackage Process Phases
swpackage reads the PSFI. Selection
swpackage analyzes the packaging tasks and requirements before actually packaging the
software to the target depot or tape. swpackage compares the software to be packaged
against the target depot to make sure the packaging operation will be successful.
II. Analysis
swpackage packages the source files and information into a product object, and inserts
the product into the distribution depot. swpackage creates the depot but does not register
it. You must have appropriate SD-UX permission to create this new depot on the local host.
If the target (destination) is a tape media, a temporary depot is created.
III. Build
(Optional) This phase occurs only if you are packaging to a distribution tape. swpackage
copies the source files and a temporary depot catalog to the tape. (Note that swpackage
cannot compress files when writing to a tape.)
IV. Make Tape
10.5 Packaging the Software (swpackage) 195