Ignite-UX Reference (March 2010, B3921-90005)

make_config(1M) make_config(1M)
NAME
make_config − build Ignite-UX configuration files for SD depots
SYNOPSIS
/opt/ignite/bin/make_config -r release [ -o os_release ][-l level][-p ][-s
release_relative_source_depot] [ -v ][-x option][-d percent][-? ]
/opt/ignite/bin/make_config -s source_depot -c configuration_file [ -a 700|800|both ]
[ -f software_file][-o os_release][-l level][-p ][-d percent]
[ -v ][-x option][-? ]
DESCRIPTION
make_config constructs Ignite-UX configuration files which correspond to Software Distributor (SD)
depots. When an SD depot is used as part of the Ignite-UX process, it must have a config file which
describes the contents of the depot to Ignite-UX. This command may automatically construct such a config
file given the name of an SD depot on which to operate. This command should be run when adding or
changing a depot that will be used by Ignite-UX.
make_config only generates information for SD bundles within a depot. All HP software is packaged in
SD bundle form; products not contained in bundles are ignored.
make_config uses the names of the depot(s) and configuration file(s) to give it clues about what type of
configuration file to produce. If the name contains a "700", the resulting configuration file will only be
used on Series 700 target machines. If the name contains an "800", the resulting configuration file will only
be used on Series 800 target machines. The -a 700|800|both option performs a similar function, with
appropriate arguments, to specify the type of configuration file.
Generally make_config produces a sw_sel clause for each bundle it finds in the depot. The tag for
the sw_sel is the same as the bundle tag. When multiple bundles in the depot have the same tag (but dif-
ferent architecture, revision, or vendor attributes), make_config will build multiple sw_sel clauses
with tags differentiated by revision, architecture, or vendor, and make them exrequisites of each other (see
instl_adm(4)). If these bundles are "always load" bundles, this will result in an error and no file will be pro-
duced. make_config produces a header in the file that shows the name of the file produced, its creation
time, and the Ignite-UX version installed when make_config was used to create the file. Note that later
versions of Ignite-UX should always be able to parse a config file produced by an earlier version.
Errors are always logged to stderr. More detail may often be found in the log file at:
/var/opt/ignite/logs/make_config
Options
make_config recognizes the following options:
−r release
Construct configuration files for each of the depots found in the default depots directory
for the specified release. Ensure that the newly constructed configuration files are
included in each of the configuration clauses for the specified release in the file
/var/opt/ignite/data/INDEX.
For example, if the specified release is B.11.23, a configuration file will be generated for
each depot found in the /var/opt/ignite/depots/Rel_B.11.23 directory.
The generated configuration files will be placed in the
/var/opt/ignite/data/Rel_B.11.23 directory. The configuration files will
have the same name as their associated depots, with an appended _cfg. For instance,
the /var/opt/ignite/data/Rel_B.11.23/core_700_cfg configuration file
will be generated from the
/var/opt/ignite/depots/Rel_B.11.23/core_700 depot.
If −s release_relative_source_depot is also specified, the depot named must be relative
to the directory implied from the release specified by -r.
1