Use > Software management > Package type reference > HP-UX packages

HP-UX packages

Depots are the container packages for HP-UX. Depots have the following characteristics:

  • A depot either contains products that contain filesets, or it contains patch products that contain patch filesets.
  • When a depot contains multiple products and filesets, frequently only a subset is installed because users might want to install only certain products or filesets.
  • A depot is a special type of directory formatted for use by HPE Software Distributor (SD-UX) commands. SD-UX, a software management system, is the distribution mechanism for all HPE Software for HP-UX.
  • A depot can be a local directory, a CD-ROM, tape, or it can reside on a server on the network.
  • Multiple depots can be created for different applications or purposes.
  • Users upload depots to the Software Repository in TAR format.
  • When the software in a depot is compatible with multiple versions of HP-UX, upload the depot to the Software Repository for all appropriate versions.
  • Depots cannot be differentiated by a hardware platform, such as s700 or s800.
  • HP-UX depots have two basic formats:
    • Directory: The format for depots saved on a server or CD-ROM.
    • Tape: The format for standalone depot files and the format required for uploading HP-UX packages into SA.

Products and filesets are the installable packages for HP-UX. They have the following characteristics:

  • Products and filesets are versioned.
  • Filesets are the smallest installable unit. A fileset can belong to only one product, but can be included in multiple subproducts or bundles.
  • Subproducts are logically related filesets and are not versioned; for example, X11.Manuals.
  • Products are supersets of filesets.
  • Bundles are logical groups of filesets; for example, HP-UX Support Tools Bundle.
  • SA supports products, filesets, and patch products as installable software.

Note
SA does not support bundles (which are abstract sets of filesets, drawn from depots) or subproducts by automatically creating policies for bundles and subproducts when users upload depots. However, users can still model bundles and subproducts by creating policies for them and attaching the filesets for the bundles and subproducts. SA does not support using HP-UX code words.

When a user uploads a depot, SA performs the following actions:

  • Opens the depot and parses its metadata.
  • Automatically creates entries in the list of packages for the products and filesets in the depot and registers them as installable.
  • Registers the depot as a non-installable package.

If a depot contains different software for specific versions of HP-UX, create OS-specific depots for each HP-UX version and upload the depots to the Software Repository. The SA Client does not check the OS compatibility of the products and filesets in a depot when a user uploads the depot. When adding products or filesets to a software policy, the products and filesets can be added only when the associated OS of their depot matches the OS specified for the software policy.

  • The format of HP-UX version information can be inconsistent, making it difficult to determine whether one version is older than another when installing a package that has another version already installed. SA attempts to install it anyway. An error results if a newer version is already installed.

SA does not provide alternate root support for HP-UX. Do not include commands that require alternate root support in the Install Flags text box of the Packages: Properties page. By default, the HP-UX swinstall command does not replace a newer version of a fileset or product with an older version. However, SA does overwrite newer versions of filesets and products with older versions. SA does not support relocating packages for HP-UX.

Depot metadata

SA uses the metadata contained in depots when creating the package entries in the list of packages. A depot contains the following metadata:

  • The name, version, and description of each product in the depot
  • The list of filesets in each product in the depot
  • The name, version, and description of each fileset in the depot

Preparing for HP-UX package management

Before you upload a depot to the Software Repository:

  1. Convert the depot on the installation media (CD-ROM) from directory format to tape format by using the swpackage command:

    swpackage -x media_type=tape -s <directory depot> <software selection> @ <file depot>
  2. Split the depot into depots for each product.

For more information on creating a script to automate this step, see Example: File – Script to split a depot by product and Example: File – Script to split a depot by bundle.

Example: Commands – Converting a depot

The following example shows the commands used to create a Quality Pack file depot from the Support Plus CD-ROM for HP-UX 11.00:

  1. Mount the directory on the CD-ROM that contains the Quality Pack file depot:
    mount -F cdfs /dev/dsk/c2t1d0 /cdrom
  2. Convert the depot on the CD-ROM from directory format to tape format by using the swpackage command:

    swpackage -x media_type=tape -s /cdrom/QPK1100 QPK1100 @ \
    /var/tmp/QPK1100.depot

    Entering this command copies the QPK1100 bundle contained in the depot to a file that can be uploaded into SA.

Example: File – Script to split a depot by product

# This is an example script that splits a depot into individual
# product depots that can then be uploaded to the HPE
# Software Repository
 
for product in `swlist -l product -s <location of depot> | \
	cut -f1 | grep -v ^# | grep ‘[A-z]’`
do
swpackage -x media_type=tape -s <location of depot> $product \
	@ /var/tmp/$product.depot
done

Example: File – Script to split a depot by bundle

# This splits a depot into individual bundle depots that can
# then be uploaded to the HPE Software Repository
 
for bundle in `swlist -l bundle -s <location of depot> | \
	cut -f1 | grep -v ^# | grep ‘[A-z]’`
do
swpackage -x media_type=tape -s <location of depot> $bundle \
	@ /var/tmp/$bundle.depot
done

Send Help Center feedback