Ignite-UX Custom Configuration files

pac
kage the bundle in the depot. The example swpackage command contains the path given to
PSF “as is”. You may need to change the path to the PSF file in the example if you change your
current working directory or move the PSF file.
With the –r option, you can specify a revision for a bundle. This allows you to create bundle
wrappers with revision numbers, enabling you to better manage changes to software.
The examples in this section operate on the following depot:
# swlist -d @ /var/opt/ignite/depots/Rel_B.11.23/patches
# Initializing...
# Contacting target "test"...
#
# Target: test:/var/opt/ignite/depots/Rel_B.11.23/patches
#
#
# No Bundle(s) on test:/var/opt/ignite/depots/Rel_B.11.23/patches
# Product(s):
#
PHCO_31622 1.0 Cumulative changes to frecover(1M)
PHCO_31634 1.0 Cumulative changes to pax(1)
PHCO_33431 1.0 tar(1) catalogs ; directory timestamp
PHCO_36056 1.0 find(1) cumulative patch
Because there are no existing bundles, using the –b option or the –B options achieves the same
result.
The following example bundles all the patches:
# make_bundles -b -i -n "PB_Sept_2007" \
> -t "backup commands patches for Sept 2007" \
> -r 1.0 /var/opt/ignite/depots/Rel_B.11.23/patches
Generating list of unbundled filesets...
======= 08/30/07 16:25:12 EST BEGIN swpackage SESSION
* Session started for user "root@test".
* Source: test:/var/tmp/psf.28120
* Target: test:/var/opt/ignite/depots/Rel_B.11.23/patches
* Software selections:
*
* Beginning Selection Phase.
* Reading the Product Specification File (PSF)
"/var/tmp/psf.28120".
* Reading the bundle "PB_Sept_2007" at line 11.
* Selection Phase succeeded.
* Beginning Analysis Phase.
* Analysis Phase succeeded.
* Beginning Package Phase.
* Packaging the bundle
27