User's Guide

Similar to above, except that when the ~ operator is used
instead of =, then the sw_sel tags listed are treated as
fnmatch(3C) regular expressions that can be used to match
any selection fitting the given pattern. (Note that this operator uses
fnmatch
(3C) pattern matching expressions. Other uses of the ~ operator in
the configuration file, uses extended regular expressions. This
difference is for compatibility with some existing data.) The category
string can be specified (with a "." separator) in order to limit the
matches to those selections in the specified software category.
The following example uses expression matching:
sw_sel "perl" {
description = "Perl Programming Language"
sw_source = "core"
sw_category = "OrderedApps"
sd_software_list = "perl,r=B.5.6.1.C,a=HP-UX_B.11.11_32/64,v=HP"
impacts = "/opt" 49480Kb
load_with_any ~ "HPUXBaseOS" . "*"
}
The preceding load_with_any automatically selects perl to be loaded when any sw_sel with
a category of HPUXBaseOS is selected.
The load_with_all configuration item enables you to specify a list of sw_sel clauses that must
all be selected automatically to select a sw_sel for installation:
load_with_all = tag-string [[ & tag-string ]...]
Specifies that when all the sw_sels listed are selected,
then this sw_sel should be selected as well. Multiple tags
may be listed separated by the & character.
If multiple load_with_* keywords are specified, the list of
tag-strings will be added to any already listed for the
respective keyword.
The load_with_* configuration items automatically deselect sw_sel clauses as appropriate
when you are changing what sw_sel clauses are selected for installation (that is, enforce
dependencies). There is one exception to this rule: if you manually select a sw_sel for installation
and it has any load_with_* configuration items that are not satisfied, it cannot be automatically
deselected because it was manually selected.
Installing patches
Patches are best installed using software configuration rather than command hooks like
"post_load_cmd" because a new kernel is built after all software is installed. If you install
patches using command hooks, a new kernel is not built, which may cause some unusual behavior
in HP-UX where commands depend on kernel functionality that is not in the kernel.
Configuration for volume and disk groups
In this section, the default configuration file for an HP-UX release is assumed always to be included
before any others. Because internal variables defined by that configuration file must be set for
Ignite-UX to work correctly.
129