Ignite-UX Custom Configuration files

You ca

n use the –b option when you want to operate on all of the unbundled product filesets in a

depot and the –B if you want to operate on all product filesets within a depot.

You can use the –p and –f options to modify what the –b option does (although you cannot use

them with the –B option). The –p option creates one bundle for every product in the depot, making

–B unnecessary. When used with the –b option, the command only processes products that are

not already contained within a bundle. The –f option has a similar function to –p but it operates

at the fileset level; that is, when you use –f it causes a bundle to be created for all filesets in the

depot (except when –b is used as well; then only filesets in products not already contained with a

bundle are processed).

The form of make_bundles that you use depends upon what you want to do with it. The

following sections demonstrate what can be done with three forms of the command.

The make_bundles first form

The first form of make_bundles uses –b or –B and not –p or –f, so you can operate either on all

unbundled product filesets or on all product filesets. This form, however, can only create one

bundle wrapper.

/opt/ignite/bin/make_bundles {-b|-B} [-i] [-n name] [-t title] [-c

category] [-o psf] [-r revision] depot_path

With the addition of the –i option, you can set the is_reference SD bundle attribute to TRUE.

When set to TRUE, the is_reference causes the bundle wrapper to be installed whenever a

product or fileset within a bundle is installed. When set to FALSE, the bundle wrapper is installed

only when selected. HP-UX patch bundles always have the is_reference set to TRUE because

they can then be installed with either patch_match_target or autoselect_patches set to

TRUE. In contrast, if is_reference is set to FALSE, the bundle wrapper for the the HP-UX patch

bundle would not be installed with the patches since SD selects patches to be installed, not bundles

(leaving the patches unbundled after installation). This allows the bundle wrapper to be

automatically installed when patches have been automatically selected for installation by SD. (This

can happen if there are software bundles in the same depot as the patches that are installed, and

the patches are for filesets in the bundles.)

Important:

You should always use the –i option when defining bundles that contain

patches so t

hat the bundle definition is installed when any patch from

the bundle is installed.

With the –n option, you can give the bundle a name, which must be 16 characters or fewer. With

the –t option, you can give a longer descriptive title for the bundle, which must be 256 characters

or fewer and can only contain one line. With the –c option you can assign a category to the

bundle; the default, if not given, is to make the bundle uncategorized. See the section "Categories

and other Ignite-UX software attribu

tes" on page 118 for more information on software categories.

With the –o option, make_bundles writes ou

t a Product Specification File (PSF) instead of

modifying the target depot. This option is useful if you need to make customizations to the PSF

before applying the changes to the depot. The PSF contains the swpackage command required to