Software Distributor Administrator Guide (September 2010)

file -v 4
file -v 5
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 248)).
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 125)).
The swpackage Process
The swpackage process includes up to four phases:
10.5 Packaging the Software (swpackage) 253