Ignite-UX Custom Configuration files

sw_sel "EE pack" {
description = "Software Apps for Electrical Engineering IPF clients"
sw_source = "Per-Discipline Packs"
archive_type = gzip tar
archive_path = "ee_client_archive_IPF.gz"
sw_category = "Disciplines"
impacts = "/var" 18852Kb
impacts = "/usr" 35202Kb
impacts = "/" 3Kb
}
The next example sw_sel defines a different application, but shares all of the same attributes.
sw_sel "ME pack" {
description = "Software Apps for Mechanical Engineering IPF clients"
sw_source = "Per-Discipline Packs"
archive_type = gzip tar
archive_path = "me_client_archive_IPF.gz"
sw_category = "Disciplines"
impacts = "/var" 35517Kb
impacts = "/usr" 19479Kb
impacts = "/opt" 85338Kb
impacts = "/" 96Kb
}
}
SD and archive bitness comparison
You may have noticed an issue with the non-SD application example. Special effort was taken to
ensure that a 64-bit version of the product was not installed on a 32-bit system. You could set SD
to do this automatically. On PA-RISC systems, you would set the SD attribute os_name. For
example using swlist -l fileset -a name -a os_name to look at some of the installed
filesets results in the following:
# FCMassStorage HP-UX
FCMassStorage.FCMS-ENG-A-MAN HP-UX
FCMassStorage.FCMS-INIT HP-UX
FCMassStorage.FCMS-JPN-E-MAN HP-UX
FCMassStorage.FCMS-JPN-S-MAN HP-UX
FCMassStorage.FCMS-KRN HP-UX:*64
FCMassStorage.FCMS-RUN HP-UX
FDDI-KRN-COM HP-UX
FDDI-KRN-COM.FDDI467-KRN HP-UX:*64
...
Notice that os_name is set to HP-UX:*64 for some of the filesets in the previous example. In the
file, /opt/ignite/data/Rel_B.11.11/config that is included into the configuration clause
that you setup is the following configuration code:
sd_command_line += " -x os_release=" +${release}
(_hp_os_bitness == "64")
{
(!can_run_64bit)
{
ERROR += "This system model: \"" +${model}+ "\" is not supported for
running 64bit HP-UX, you must select the 32bit selection"
}
sd_command_line += " -x os_name=HP-UX:64 "
186