Glossary

An attribute that names a previous version of a fileset. This is used to match filesets on a target system. If the match_target option is set to true, SD-UX matches the ancestor fileset name to the new fileset name.

The default relationship for specifying one or more dependency attributes (corequisites or prerequisites) where all dependencies must be satisfied.

An attribute that represents the operating system platform on which the product runs. (e.g., IA/PA)

Information that describes a software elements characteristics. Attributes are an essential part of the product specification file (PSF), providing such information as a product's name, title and description.

A collection of references to filesets and/or products grouped for a specific purpose. By specifying a bundle, all products or filesets referenced in that bundle are automatically included in the operation.

The type of software being packaged.

An optional script associated with a product or fileset that is executed by swinstall during the analysis phase. The result returned by the script determines if the fileset can be installed or updated.

An optional script associated with a fileset that is executed during the swremove analysis phase. The result returned by the script determines if the fileset can be removed.

The set of commands that can be executed directly from the operating system's command shell.

An optional script associated with a fileset and automatically executed by swinstall (or manually executed by swconfig) after the installation of filesets is complete.

A software element that physically stores the elements it contains.

An optional script packaged with software or added to software by modifying the IPD. Control scripts are run during swconfig, swinstall, swremove, or swverify operations. Control scripts may include: configure or unconfigure for swconfig; checkinstall, preinstall, postinstall and configure scripts for swinstall; the checkremove, unconfigure, preremove, and postremove scripts for swremove; and the fix or verify script for swverify.

An attribute that defines the copyright for the destination depot (media) being created/modified by swpackage. It refers to the copyright information for the software product.

A dependency in which a fileset requires that another fileset be installed and configured at the same time. For example, if fileset A requires that fileset B is installed at the same time, fileset B is a corequisites.

A relationship between filesets in which one requires another in a specific manner. For example, before fileset A can be installed, it may require fileset B to be installed. SD-UX supports corequisite and prerequisite dependencies.

A fileset that has a dependency on another fileset. For example, if fileset A depends on fileset B, then B is a dependent or has a dependency on A.

A repository of software products and a catalog, organized so SD-UX commands can use it as a software source. The contents of a depot reside in a directory structure with a single, common root. A depot can exist as a directory tree on a SD-UX file system, on a CD-ROM, or as a tar archive on a tape. All depots share a single logical format, independent of the type of media on which the depot resides. Depots can reside on a local or remote system. You can package software directly into a depot or copy packaged software into the depot from elsewhere.

An attribute for products and filesets, usually a paragraph description of that product or fileset.

The path at which a file will be installed.

The filesystem structure that will be created on the target system when the software product is installed.

An optional keyword that ends the software element specification in a PSF. No value is required.

An optional keyword that ends the software element specification in a PSF. No value is required.

A collection of related files. A fileset serves as a container for files, associated file attributes, and separate control scripts. Most SD-UX operations are performed on filesets.

A program interface that takes advantage of the computer's graphics capabilities to make the program easier to use.

In packaging, an attribute that defines whether a product can be installed to an alternate product directory or not. If specified, the attribute is set to a value of true. If not specified, the attribute is assigned a value of false.

In packaging, an attribute that describes the type of systems on which the product will run. (If not specified, the keyword is assigned a wildcard value (*) meaning it will run on all machines. If there are multiple machine platforms, you must separate each machine designation with a vertical bar ( | ). (e.g., IA64)

Physical data storage media on which software is stored, such as tape, CD-ROM, or DVD.

multiple architecture - A single product that contains different versions of the same fileset which differ by their architecture attribute.

An attribute whose inclusion in the product specification file is optional, will not effect the users ability to create a software package using swpackage.

See OR dependency set.

Used to identify multiple corequisites or prerequisites attributes for a fileset where only one of the set must satisfy the dependency.

See OR dependency set.

Software designed to update specific bundles, products, subproducts, filesets, or files on your system. By definition, patch software is packaged with the is_patch attribute set to true.

An optional script associated with a fileset that is executed by swinstall after the corresponding fileset has been installed or updated.

An optional script associated with a fileset that is executed by swremove after the corresponding fileset has been removed.

An optional script associated with a fileset that is executed by swinstall before installing or updating the fileset.

An optional script associated with a fileset that is executed by swremove before removing the fileset.

A dependency in which one fileset requires another fileset to be installed and configured before the first fileset can be installed or configured. For example, fileset A may require that fileset B is installed before fileset A can be installed. Therefore, fileset B is a prerequisite for fileset A.

A collection of filesets, subproducts and/or control scripts that form a set of related software.

A file that defines the structure of a software package and maps your source filesystem area to create the destination filesystem on a target system. A PSF identifies the software package according to its attributes, contents, compatibilities, and dependencies.

This attribute provides either the location of the text file containing the README information or the text value itself.

A software element that virtually stores (or references) the data for the software elements it contains.

A software element that is external to the local PSF.

An attribute whose inclusion in the product specification file is mandatory and will cause an error if the user attempt to create a software package using swpackage.

The root directory of a system (/).

The directory on a target system in which all the files of the selected products will be installed. The default (/), can be changed to install into a directory that will eventually act as the root to another system.

HP-UX Software Distributor. The format and syntax of SD-UX software in depots.

A SD-UX format structure that contains one or more software products that can be installed on other systems or copied to other depots.

A product specification file (PSF) is comprised of five software elements that can be packaged, distributed, installed, or managed by Software Distributor (SD-UX). A software element may be a file, fileset, product, subproduct, or bundle.

Installable Software Distributor format software created with swpackage. Packaged software can be placed in a depot for distribution.

Attributes that are used to define a relationship or an assignment between a designated software element and other software element(s). Software specification attributes are defined using a software_specification value type.

Defines a software element in great detail using the SD software_selection syntax, including information such as revision, architecture and version.

The directory and associated files which comprise your software product. Files are mapped from the source filesystem to create the destination filesystem on a target system via the PSF.

A software element that serves as a reference for groups of logically related filesets. A subproduct can be used to partition a product that contains many filesets or to offer the user different views of the filesets. Subproducts are optional and considered an advanced packaging topic.

A SD-UX command that installs software.

A SD-UX command that lists software elements, their attributes, and their organization. It lists both installed software and software contained within a depot.

A SD-UX command that uses a product specification file (PSF) to organize software products and package them into a depot. The depot can be accessed directly by SD-UX commands or mastered onto CD-ROM or tape.

A SD-UX command that removes previously installed software or removes packaged software from a depot.

A SD-UX command that verifies installed software or depot software for correctness and completeness.

In packaging, an attribute that defines the distribution tag or software element's name attribute for the destination depot (media).

An optional script associated with a fileset that is executed by swremove before the removal of filesets begins.

The vendor for the software being packaged. If a vendor specification is included in the PSF, the vendor and tag attributes are required for swpackage.

An attribute you define to provide additional information about a software package. A vendor defined attribute (VDA) may be created for any software element in the product specification file.

Associates the product or bundle with the last-defined vendor object, if that object has a matching tag attribute.