The sw_source definition for the core operating system depot contains the information needed to define an SD depot. The load_order of 0 (zero) is important for a core operating system depot. The load order determines the order in which Ignite-UX loads the software. Other software products can be loaded at load order 0 except when the core operating system is an archive rather than a depot. When loading a core operating system archive, you can have one and only one sw_sel installed at load_order 0.

If you place any other software in the core operating system depot, swinstall resolves dependencies from the source depot that it is installing from before attempting to satisfy dependencies from the target. If you were to use "-x reinstall=true" on a swinstall command to install a product that had dependencies on the core operating system, you could also reinstall parts of the core operating system along with the product. The easiest way to prevent this from happening is to avoid placing additional software products in the core operating system depot or to never load software from that depot outside of Ignite-UX (you may know to never use –

xreinstall=true but you may want to use that depot in the future with that option).

Next are the sw_sel definitions of the 32-bit and 64-bit Base HP-UX bundles. Effectively the same definitions are generated for a core operating system depot. Never include the definitions of multiple core operating system depots within one clause in the /var/opt/ignite/INDEX file because they start to override each other and cause issues with the install.

In the preceding example, the impacts statements for the bundles have been removed to make the clauses easier to read. Now, look at the 64-bit sw_sel clause. The name of the sw_sel clause is HPUXBase64. Its description is set to HP-UX 64bit Base OS. It has a sw_source set to core that was defined earlier. Always try to place the sw_source definition and the software products that reference it in the same configuration file to prevent dependencies between configuration files.

Next is the software category. For more information on categories and other software attributes (including special handling for some attributes), see the section on "Categories and other Ignite-UX software attributes" because some categories are handled specially. Some categories are not shown to the user as being available for selection.

The sd_software_list next defines the software that this sw_sel references. In this case, it is the bundle HPUXBase64 with the attributes revision ("r=") B.11.11, architecture ("a=") HP- UX_B.11.11, and vendor ("v=") HP.

Next exrequisite = sw_category makes sure that no other software with the same software category can be selected at the same time as this bundle. This automatically unselects any other sw_sel with the same software category set. This is to prevent both the 64- and 32-bit bundles from being selected simultaneously. That is the end of the software definition.

The following example tests to see if sw_sel HPUXBase64 is selected (the surrounding parenthesis make this a test) and the variable _hp_os_bitness is set to 64, if the 64-bit Base operating system has been selected.

######################################################

##HPUX Base OS

#####################################################

sw_sel "HPUXBase64" {

description = "HP-UX 64-bit Base OS" sw_source = "core"

111