Software Distributor Administration Guide for HP-UX 11i

Installing Software
Installation with swinstall
Chapter 280
Once multiple versions of software are installed into a location, you can
manage them by specifying the product attribute in the software
specification of SD-UX commands. (This is as opposed to specifying other
version attributes such as revision and architecture). This lets you
install old and new versions of software at the same time and configure
both versions (if the software packaging supports it).
You can avoid unauthorized, privately installed versions of software by
controlling access to the IPD and restricting the use of the swinstall tool.
NOTE Managing multiple versions of a software product on your system
requires close attention to the cross-product dependencies that may exist
for each version. When you installing multiple versions, make sure you
also install multiple versions of the cross-product dependencies. If the
dependencies are not relocatable and each version you want to install
depends on a different version of the same product, multiple versions of
the original product cannot be installed.
Installing to an Alternate Root
Software is usually installed relative to the primary root directory (
/ ) but
you can also install to an alternate root directory.
The automatic configuration and compatibility filtering that is part of
the swinstall command is not performed when installing to an alternate
root. You can, however, perform configuration separately from
installation by using the swconfig command. See “Configuring Your
Installation (swconfig)” on page 82.
Compatibility Filtering and Checking
SD-UX normally filters out software products that are incompatible with
any selected targets. Compatible means that the architecture of the
hardware matches that required by the software (determined by the
system uname attributes). It also means that the OS version is the
proper one for the software. The actual check for incompatible software
is performed during the selection phase. Compatibility filtering and
checking are controlled by the allow_incompatible option and depend
on the host’s uname attributes.