Software Distributor Administration Guide for HP-UX 11i

Introduction to Software Distributor
SD-UX Concepts
Chapter 1 33
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” on
page 59 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)
• Be in the proper software state (the dependency must be configured
if the software dependent on it is to be installed and configured,
installed if software dependent on it is to be installed but not
configured, or available if the software dependent on it is to be
copied)
• Be free of errors (for example, no incompatibility errors).