 |
» |
|
|
|
A software package is created from a hierarchy of software
elements. The hierarchy provides the structure needed by the filesystem
to logically identify packaged files. A software package also contains
metadata specific to each software element. The metadata is generated
by setting attribute values. This is all accomplished through the
creation of a PSF which defines the software package.Once the software
package is created, you can create a software depot which acts as
a repository for your software products. Software depots can be
managed using SD-UX commands.The packaging process lets you create
depots. The PSF is flexible enough to fit many software build requirements
and manufacturing process needs. Before you begin packaging software,
ensure the following: SPB is installed
and configured on the system where you intend to create your software
package. The software to be packaged
is installed on the packaging system, or the necessary files are
available remotely.
Organizing
Filesystems | |
One of the
first steps in packaging software is determining what files and directories
you want included in the software package. The files should follow
certain guidelines to support the configuration you want. As much as is feasible, you should group your source directories
and files so they correspond with the filesets and products you
are using in the software package. To make the maintenance of your
software package easier, when organizing your source and destination
filesystems use the following guidelines: Create
filesets with consistent file access modes (i.e., file permissions). Create directories with contents
that are directed to the same filesets. Group related files in the
source filesystem that will directly translate to the destination
filesystem.
Software
Elements | |
A software package is created from a hierarchy of software
elements, which are structured and defined in a PSF. The SPB-specific
software elements are as follows: - File
A file is the lowest level of
software element that can be contained in a software package. Files
are grouped together to create filesets. - Fileset
A fileset serves as a
container for files, associated file attributes, and separate control
scripts. A fileset is comprised of a group of files. Filesets are
grouped and contained in products. A fileset can only belong to
one product; however, a fileset may be referenced in multiple subproducts within
one product. A fileset can also be included in multiple bundles
through the product it is contained within. A minimum of one fileset
is required for a PSF. - Product
A product is a container
for filesets, subproducts, and/or control scripts specific to a
software package. Products are collections that form a set of related software.
A product can contain one fileset or multiple filesets. Products
can contain filesets specific to different versions of the product
and different hardware platforms. All these different filesets can
be packaged together for distribution. A minimum of one product
is required for a PSF. - Subproduct
A subproduct is a reference
to groups of related filesets within a product. For example, you
might create a subproduct that references a fileset grouping for
the entire runtime configuration, manuals, or demonstration versions
of the product. It is important to remember that subproducts only
reference filesets and do not physically contain the fileset. The
use of subproducts is optional and considered an advanced feature. - Bundle
A bundle is a reference
to filesets, subproducts and/or products. Bundles may reference
collections of filesets that belong to several different products.
Creating bundles consisting of multiple filesets allows you to treat
several filesets as a single entity. By specifying a bundle, all
filesets under the bundle are included in the operation. It is important
to remember that bundles only reference filesets, products, and/or
subproducts and do not physically contain these software elements. The
use of bundles is optional and considered an advanced feature. - Vendor
A vendor is a software
element that lets you add additional, detailed information about
a PSF. - Category
A category is a software
element that can be used as a selection mechanism for a software
package. This software element contains additional information about
the category. The category information is referred to by the category_tag attribute within a product, bundle, subproduct, or fileset.
Software
Package Hierarchy | |
The software package
hierarchy provides the structure needed by the filesystem to identify
packaged files. Figure 2-2 “Software Package Hierarchy” provides a graphical representation of the hierarchical
structure to which a valid PSF must adhere. Containment vs. ReferenceThere are two types of relationships that exist within the
hierarchical structure of a software package: containment and reference.
If a software element acts as a container, then the software element(s)
it is comprised of are physically contained. If a software element
acts as a reference, then the software element(s) it is comprised
of are virtually contained.The difference between a containment
relationship and a reference relationship can be illustrated by
the notion that a bundle can be removed without actually removing
the software elements that it references. However, removing a product
always removes the filesets it contains, and the files contained
in the filesets. Table 2-1 “Structural Elements: Functions and Relationships” provides a summary
of a software package's structural elements, their functions, and
their relationship to other elements. The structural elements are
numbered to correspond with Figure 2-2 “Software Package Hierarchy”: Table 2-1 Structural Elements: Functions and Relationships | Structural Element | Function | Relationship |
|---|
| Installed Software (1) | A delivered and installed software package. | The installed software is a valid and complete software
package. | | Product (2) | A collection of related filesets and optionally, subproducts
and control scripts. | A product is a container for
filesets, subproducts, and optionally, control scripts. | | Bundle (3) | A collection of related filesets, subproducts, and/or
products. | A bundle is a reference for
groups of filesets, subproducts, or products. | | Fileset (4) | A grouping of related files and control scripts. | A fileset is a container for
files and control scripts.Filesets are contained in products. | | Subproduct (5) | A grouping of related filesets. | A subproduct is a reference for
groups of related filesets within a single product. | | Control File (6) | A control file performs checks and other tasks in
the software package. | Control files (scripts) are contained in
one or more filesets and/or products. | | File (7) | Files serve as the building blocks for a software
package. | Files are contained in one
or more filesets. |
|
Printable version
