Ignite-UX Custom Configuration files

}
}
sw_sel "KRMonitor" {
description = "EMS Kernel Resource Monitor"
sw_source = "/var/opt/ignite/depots/T1335AC_A.02.03.02"
sw_category = "HPUXAdditions"
sd_software_list = "KRMonitor,r=B.11.11.04,a=HP-UX_B.11.11_32/64,v=HP"
...
Using both of these configuration files together (or the configuration file
/var/opt/ignite/data/Rel_B.11.11/vpars_A.02.03.02.cfg with anything else)
causes conflicts unless manual changes are made.
When make_config finds two or more bundles of the same name in one depot, it places a
combination of the revision, architecture, and vendor into the sw_sel clause name
(enough of one or more of them to make the sw_sel name unique). When make_config finds
that a bundle name is unique in the depot, it does not place the revision, architecture, or
vendor in the name of the sw_sel clause.
If you included both of the preceding configurations, the duplicate names (in this case "T1335AC")
would cause issues. The information in the first definition of the sw_sel is overruled with the
information from the second definition. The reason for this is that sw_sel clauses are stored by
name, T1335AC, without regard to the configuration file from which they were derived.
To prevent this issue, you need to distinguish between the products in the first configuration file and
the second configuration file. Change vPars A.02.02 to the following:
sw_sel "T1335AC,r=A.02.02.00" {
(_hp_os_bitness == "64") {
...
exrequisite="T1335AC,r=A.02.03.02"
visible_if = TRUE
}
else {
visible_if = FALSE
}
}
This puts the revision number into the name of the sw_sel. When you have multiple versions
of a product available to an installation session (but potentially in different depots), it is a good
idea to manually include the version number in the configuration. In the second configuration
file the same product needs to become the following:
sw_sel "T1335AC,r=A.02.03.02" {
(_hp_os_bitness == "64") {
...
exrequisite="T1335AC,r=A.02.02.00"
visible_if = TRUE
}
else {
visible_if = FALSE
}
}
109