Software Distributor Administration Guide for HP-UX 11i

Creating Software Packages
Packaging Tasks and Examples
Chapter 10 361
Repackaging or Modifying a Software Package
There are two types of repackaging:
1. Adding to or modifying a fileset in an existing product.
• Editing the PSF by adding a new fileset definition or changing an
existing fileset’s definition.
• Running swpackage on the edited PSF, specifying the
new/changed fileset on the command line:
swpackage -s
psf <other options> \
product.fileset @ depot
This invocation works regardless of whether subproducts are
defined in the product.
• If you change a fileset by changing its tag attribute, swpackage
cannot correlate the existing, obsolete fileset with the new fileset.
Both become part of the changed product. To get rid of the
obsolete (renamed) fileset, use swremove:
swremove -d
product.old_fileset @ depot
2. Modifying an entire existing product.
• Editing the PSF by adding new fileset definitions, changing
existing fileset definitions, deleting existing fileset definitions or
changing the product’s definition (product-level attributes).
• Running swpackage on the PSF, specifying the product on the
command line:
swpackage -s
psf <other options> product @ depot
• If you have deleted some fileset definitions in the PSF or
modified a fileset by changing it’s tag attribute, swpackage will
produce warning messages about the existing filesets that are
not part of the modified product’s definition (in the PSF). The
existing filesets plus the new filesets in the product’s definition
(in the PSF) will all be contained in the modified product.
The warnings are produced during analysis phase, and are only
produced when the whole product is being repackaged (as
opposed to subsets of the product).