Verifying and Transferring a Package

This chapter describes how to verify your package's integrity and transfer it to a distribution medium, such as floppy disk or a CD-ROM.

This is a list of the overview information in this chapter:

• "Verifying and Transferring a Package Task Map"

• "Installing Software Packages"

• "Verifying the Integrity of a Package"

• "Displaying Additional Information About Installed Packages"

• "Removing a Package"

• "Transferring a Package to a Distribution Medium"

Verifying and Transferring a Package Task Map

The table below describes the steps you should follow in order to verify your package's integrity and transfer it to a distribution medium.

Table 4-1 Verifying and Transferring a Package Task Map

Installing Software Packages

Software packages are installed using the pkgadd command. This command transfers the contents of a software package from the distribution medium or directory and installs it onto a system.

This section provides basic installation instructions for installing your package in order to verify that it installs correctly.

The Installation Software Database

Information for all packages installed on a system is kept in the installation software database. There is an entry for every object in a package, with information such as the component name, where it resides, and its type. An entry contains a record of the package to which a component belongs; other packages that might reference the component; and information such as path name, where the component resides and the component type. Entries are added and removed automatically by the pkgadd and pkgrm commands. You can view the information in the database by using the pkgchk and the pkginfo commands.

Two types of information are associated with each package component. The attribute information describes the component itself. For example, the component's access permissions, owner ID, and group ID are attribute information. The content information describes the contents of the component, such as file size and time of last modification.

The installation software database keeps track of the package status. A package can be either fully installed (it has successfully completed the installation process), or partially installed (it did not successfully complete the installation process).

When a package is partially installed, portions of a package may have been installed before installation was terminated; thus, part of the package is installed, and recorded in the database, and part is not. When you reinstall the package, you are prompted to start at the point where installation stopped because the pkgadd command can access the database and detect which portions have already been installed. You can also remove the portions that have been installed, based on the information in the installation software database using the pkgrm command.

Interacting with the pkgadd Command

If the pkgadd command encounters a problem, it first checks the installation administration file for instructions. (See admin(4) for more information.) If no instructions exist, or if the relevant parameter in the administration file is set to ask, the pkgadd displays a message describing the problem and prompts for a reply. The prompt is usually Do you want to continue with this installation?. You should respond with yes, no, or quit.

If you have specified more than one package, no stops installation of the package being installed but pkgadd continues with installation of the other packages. quit indicates that pkgadd should stop installation of all packages.

Installing Packages on Standalones or Servers in a Homogeneous Environment

This section describes how to install packages on a standalone or a server system in a homogeneous environment.

How to Install a Package on a Standalone or Server

1. Build your package.

   See "Building a Package", if needed.

2. Log in to the system as superuser.

3. Add the software package to the system.

   # pkgadd -d device-name [pkg-abbrev...]

   -d device-name	Specifies the location of the package. Note that device-name can be a full directory path name or the identifiers for a tape, floppy disk, or removable disk.
   pkg-abbrev	Is the name of one or more packages (separated by spaces) to be added. If omitted, pkgadd installs all available packages.

Where to Go Next

If you are ready to go to the next task, see "How to Verify the Integrity of Your Package".

Example--Installing Packages on Standalones and Servers

To install a software package named pkgA from a tape device named /dev/rmt/0, you would enter the following command:

# pkgadd -d /dev/rmt/0 pkgA

You can also install multiple packages at the same time, as long as you separate package names with a space, as follows:

# pkgadd -d /dev/rmt/0 pkgA pkgB pkgC

If you do not name the device on which the package resides, the command checks the default spool directory (/var/spool/pkg). If the package is not there, the installation fails.

Verifying the Integrity of a Package

The pkgchk command enables you to check the integrity of packages, whether they are installed on a system or in package format (ready to be installed with the pkgadd command). It confirms package structure or the installed files and directories, or displays information about package objects. The pkgchk command can list or check the following:

• The package installation scripts.

• The contents or attributes, or both, of objects currently installed on the system.

• The contents of a spooled, uninstalled package.

• The contents or attributes, or both, of objects described in the specified pkgmap file.

For more information about this command, refer to pkgchk(1M).

The pkgchk command performs two kinds of checks. It checks file attributes (the permissions and ownership of a file and major/minor numbers for block or character special devices) and the file contents (the size, checksum, and modification date). By default, the command checks both the file attributes and the file contents.

The pkgchk command also compares the file attributes and contents of the installed package against the installation software database. The entries concerning a package may have been changed since the time of installation; for example, another package may have changed a package component. The database reflects that change.

How to Verify the Integrity of Your Package

1. Install your package.

   See "How to Install a Package on a Standalone or Server", if needed.

2. Verify the integrity of your package.

   # pkgchk [-v] [-R root-path] [pkg-abbrev...]

   -v	Lists files as they are processed.
   -R root-path	Specifies the location of the client system's root file system.
   pkg-abbrev	Is the name of one or more packages (separated by spaces) to be checked. If omitted, pkgchk checks all available packages.