Ignite-UX Custom Configuration files

sw_category = "HPUXBaseOS"
sd_software_list = "HPUXBase64,r=B.11.11,a=HP-UX_B.11.11_64,v=HP"
...
exrequisite = sw_category
}
(sw_sel "HPUXBase64") {
_hp_os_bitness = "64"
}
The following example is the definition of the 32-bit Base HP-UX bundle. It is very similar to the 64-
bit example. It also has the exrequisite = sw_category attribute that prevents the selection
of the 32-bit and 64-bit Base HP-UX bundle at the same time.
sw_sel "HPUXBase32" {
description = "HP-UX 32-bit Base OS"
sw_source = "core"
sw_category = "HPUXBaseOS"
sd_software_list = "HPUXBase32,r=B.11.11,a=HP-UX_B.11.11_32,v=HP"
...
exrequisite = sw_category
}
(sw_sel "HPUXBase32") {
_hp_os_bitness = "32"
}
Next are the operating environment (OE) definitions for the Base HP-UX 11i v1 OEs. These
definitions determine whether the system can run a 64-bit operating system or not. Ignoring the
contents of the sw_sel clauses, the sw_sel "OE90BaseOS64" is automatically selected if the
system can run 64-bit HP-UX. The visible_if prevents the Operating Environment (OE) from
being seen if the system cannot run a 64-bit version of HP-UX).
init sw_sel "OE90BaseOS64" {
description = "HP-UX 11i Base OS-64bit"
sw_source = "core"
sw_category = "HPUXEnvironments"
corequisite = "HPUXBase64"
visible_if = can_run_64bit
} = (can_run_64bit)
The 32-bit OE is only visible if the system can run a 32-bit version of HP-UX; some older systems
can run either. The 32-bit OE is automatically selected if the system cannot run 64-bit HP-UX, or if
the system can run 32-bit HP-UX and the 64-bit Base OE is not currently selected (so you must end
up with one or the other selected).
init sw_sel "OE91BaseOS32" {
description = "HP-UX 11i Base OS-32bit"
sw_source = "core"
sw_category = "HPUXEnvironments"
corequisite = "HPUXBase32"
visible_if = can_run_32bit
} = (! can_run_64bit) | (can_run_32bit) & !(sw_sel "OE90BaseOS64")
Now you have some code selecting the model it runs on and choosing a language (the sw_sel
clause for "English" is not shown in this section but it does exist in the configuration file).
112