make_bundles.1m (2012 03)

m
make_bundles(1M) make_bundles(1M)
NAME
make_bundles - create SD bundles in a depot
SYNOPSIS
/opt/ignite/bin/make_bundles
{ -b| -B}[-i ][-n name ][-t
title ][-c category ][-o
psf ][-r revision ] depot_path [
-? ]
/opt/ignite/bin/make_bundles
[ -b ][-p| -f][-i ][-c category ][
-o psf ] depot_path
[
-? ]
/opt/ignite/bin/make_bundles
{ -p| -f| -B }[-i ][-c category ][
-o psf ][-l file |
product/fileset ...] depot_path [
-? ]
DESCRIPTION
make_bundles may be used to create bundle container objects in a Software Distributor (SD) depot (see
sd(4)). make_bundles is used most often when dealing with individual patches that are SD products.
Since make_config only operates at the bundle level of software objects within a depot, using
make_bundles prior to using make_config will ensure that Ignite-UX has access to all software con-
tained in the depot.
Options
The depot_path is the only required parameter. If no options other than the
-c or -o options are given,
the
-b and -p options are assumed by default.
-b Causes make_bundles to operate only on products/filesets that are not currently
contained inside a software bundle. If the -b option is given without an -f or -p
option, one bundle will be created to contain all filesets not in a bundle.
-B Causes make_bundles to create one bundle containing all products/filesets in the
depot or those specified on the command line whether they are currently in a bun-
dle or not. It cannot be given with the -b, -f,or -p options.
-p Causes make_bundles to create one bundle for each product in the depot. If
used with the -b option, only products that have contents not within an existing
bundle will be placed inside a new bundle.
The bundle names that will be created will be of the form:
b#_Product and will be
truncated to the 16-character bundle limit. The number following the
b will be
used only if the name is not unique with a simple b_ prefix.
-f Similar to the -p option, except one bundle for each fileset will be created. -f
may also be used with the -b option.
The bundle names that will be created will be of the form:
b#_ProductFileset and
will be truncated to the 16-character bundle limit. The number following the
b will
be used only if the name is not unique with a simple b_ prefix.
-i Causes make_bundles to set the is_reference attribute to true on each
bundle it creates. Bundle wrappers with is_reference set to true will
automatically be installed any time any fileset or product within the bundle is
installed. If is_reference is false, only the filesets and products selected will
be installed; the bundle wrapper will not be installed unless it is also selected.
-n name When used with the -B or when neither the -f nor -p options are used, it sup-
plies the tag name for the new bundle to be created. If not specified, it will default
to the base name of depot_path with all illegal bundle-name characters removed,
and and it will be truncated to 16 characters.
-t title When used with -B or when neither the -f nor -p options are used, it supplies
the one line description of the bundle to be created. If not specified, it will default
to depot_path .
-c category Supplies the category for the bundle(s) that will be created. The default is to leave
the bundles uncategorized.
-o psf Causes make_bundles to create a product specification file and write it to the
given psf without actually modifying the target depot. This may be useful in editing
the bundle names or descriptions before running swpackage to create the bun-
dles in the depot.
HP-UX 11i Version 3: March 2012 1 Hewlett-Packard Company 1

Summary of content (2 pages)