Ignite-UX Custom Configuration files

In conjunction with the earlier form of manage_index used to list out the names of cfg clauses in
an INDEX file, the preceding command can be used to ensure that all of the configuration files
referenced in an INDEX file are present and, as far as can be determined, correct.
Display the description of a cfg clause
This last form of manage_index is used to display the description of the cfg clause:
manage_index -x -c cfg
_clause_name [-v] [-i index_filename]
For example:
$ manage_index -x -c "testing" -i /var/tmp/INDEX
testing clause
Using the make_bundles command
Why do you need to use make_bundles?
The make_bundles command is necessary when using Ignite-UX because commands like
make_config only work with software that is contained within a bundle. Therefore, if you create
a configuration file for a depot and it contains software that is packaged only as an SD product, it
is not listed in a configuration file created by make_config.
Choosing which form of make_bundles to use
The make_bundles command has the following three forms:
/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
The make_bundles command is primarily controlled by the –B or –b options.
7
The –b option
causes make_bundles to operate on all product filesets
8
that are not contained within a bundle.
9
The –B option causes all product filesets in the depot (or those given on the command line) to be
operated on regardless of whether they are currently in a bundle or not. The different forms of the
make_bundles command, which are covered in this section, create either one or many bundles.
Each form has advantages over the other forms depending on what you want to achieve.
7
In some forms of make_bundles, the use of –b or –B is optional. However, in the most useful forms of the make_bundles command, you
will almost always use one or the other option.
8
You cannot have a standalone fileset because it must be contained within a product.
9
If you perform a swlist operation on a depot, the default output shows all bundles in the depot followed by all products not contained
within a bundle. The–b option operates only on products not contained within a bundle.
25