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

Request Requests an interactive response from the user as part of the installation or
configuration process. (Executed by swask, swconfig, and swinstall.)
Unconfigure Undoes configurations performed by configure scripts. (Executed by
swconfig and swremove.)
Unpostinstall Undoes operations performed by a postinstall script in case swinstall
must initiate recovery during the installation process. (Executed by
swinstall.)
Unpreinstall Undoes operations performed by a preinstall script in case SD must initiate
recovery during the install process. (Executed by swinstall.)
Verify Verifies the configuration of filesets or products (in addition to the standard
swverify checks.) (Executed by swverify.)
For More Information
See Chapter 11: “Using Control Scripts ” (page 201).
Environment Variables
SD-UX commands and programs are affected by external environment variables (such as language
and charset variables) and variables for use by control scripts. For a description of external
environment variables, see Chapter 11: “Using Control Scripts ” (page 201).
Software Dependencies
Software that depends on other software to install or run correctly is considered to have a
dependency. When you specify software for the swconfig, swcopy, swinstall, swremove,
swverify commands, these commands may automatically select additional software to meet
dependencies.
How Commands and Options Interact with Dependencies
Command options let you control how software dependencies are handled. For example,
dependency handling in swinstall and swcopy is affected by the enforce_dependencies
command option.
Another option that regulates dependencies is the autoselect_dependencies option. This
option determines if the system should automatically mark software for installation or copying
based on whether it meets dependencies. (See “Using Command Options” (page 37) for more
information on options.)
How Dependencies Are Resolved
For a dependency to be resolved with respect to other software on the source depot it must be:
• Complete (if the dependency is an entire product or subproduct it must exist completely in the
source depot)
• In the proper software state on the source (that is, available)
• Free of errors (for example, no incompatibility errors)
If the dependency is not available from the source during a swconfig, swcopy, swinstall,
or swverify operation, the dependency must:
• Exist on the target host
• Be complete (if the dependency is an entire product or subproduct it must be completely
installed)
22 Introduction to Software Distributor