Software Distributor (SD-UX) Administration Guide HP-UX 11i v1, 11i v2, and 11i v3 (762797-001, March 2014)

3. Check state of versions currently installed:
• If the product is non-existent or corrupt, the task issues an error that says the product
cannot be configured and to use swinstall to install and configure this product.
• If the versions currently installed are not configured and if the -u (unconfigure) option is
set, the system issues a note that the selected file or fileset is already unconfigured.
• If the state of versions currently installed is configured, the check is affected by the
reconfigure option. A note saying the fileset is already configured and will
(reconfigure is true) or will not (reconfigure is false) be reconfigured is issued.
4. Check for configuring a second version:
If the allow_multiple_versions option is set to false, an error is generated stating that
another version of this product is already configured and the fileset will not be configured. If
the option is set to true, the second version is also configured.
5. Check states of dependencies needed:
• An error or warning is issued if a dependency cannot be met. This is controlled by the
enforce_dependencies option. If enforce_dependencies is set to true the fileset
will not be configured. If enforce_dependencies is false, the fileset will be configured
anyway.
• If the dependency is a prerequisite, the configuration fails.
• If the dependency is a corequisite, the configuration of this fileset will likely succeed, but
the product may not be usable until its corequisite dependency is installed and configured.
Phase III: Configuration
In this phase, the actual software configuration takes place. Configure or unconfigure scripts are
executed and the software state is changed from installed to configured (or unconfigured).
The purpose of configuration is to configure the host for the software and configure the product
for host specific information. For example, software may need to change the host’s .rc setup, or
the default environment set in /etc/profile. Or you may need to ensure that proper codewords
are in place for that host or do some compilations. Unconfiguration reverses these steps.
The sequence of configuration tasks is shown below.
NOTE: Products are ordered by prerequisite dependencies, if any. Fileset operations are also
ordered by any prerequisites or corequisites. The loadorder_use_coreqs option can modify
load order of the filesets. For more information on loadorder_use_coreqs, see “Options Listed
Alphabetically” (page 228).
1. (Un)configure each product.
2. Run scripts for associated filesets, checking return values.
If an error occurs, the fileset is left in the installed state. If a warning occurs, the fileset will still
be configured.
3. Update the IPD to show the proper installed or configured state.
Configure scripts must also adhere to specific guidelines. For example, these scripts are only
executed in the context of the host that the software will be running on, so they are not as restrictive
as customized scripts. For more information on scripts, see Chapter 11: “Using Control Scripts ”
(page 201).
54 Installing Software