Software Distributor Administration Guide for HP-UX 11i

Creating Software Packages
Packaging the Software (swpackage)
Chapter 10348
Phase II: Analysis swpackage performs four checks during this phase:
1. Check for unresolved dependencies.
For every fileset in each selected product, swpackage checks to see if
a requisite of the fileset is not also selected or not already present in
the target depot. Unresolved dependencies within the product
generate errors. Unresolved dependencies across products produce
notes.
2. Check your authorization to package (or re-package)
products.
For each new product (a product that does not exist on the target
depot) swpackage checks the target depot to see if you have
permission to create a new product on it (insert permission). If you do
not, the product is not selected.
For each existing product (one you are re-packaging) swpackage
checks to see if you have permission to change it (write permission).
If you do not, the product is unselected.
If all products are not selected because permission is denied, the
session terminates with an error.
If the depot is a new depot or if you are packaging to a tape, this
authorization check is skipped. If you have permission to create a
new depot, then you have permission to create products within it.
Since a tape session first writes to a temporary depot then copies it to
tape, if you have permission to create a new (temporary) depot, you
can package to tape.
3. Check for software being repackaged.
For each selected product, swpackage checks to see if the product
already exists in the target depot.
• If it does exist, swpackage checks to see which filesets are being
added (new filesets) or modified.
• If it exists and all filesets are selected, swpackage checks to see if
any existing filesets have been obsoleted by the new product.