Package Component and Datastream Package Component (N1 Grid Service Provisioning System User's Guide and Release Notes for the Solaris Plug-In 2.0)

N1 Grid Service Provisioning System User's Guide and Release Notes for the Solaris Plug-In 2.0

Package Component and Datastream Package Component

Use the Package components to create components that contain the packages that you want to install or remove. For more information about creating components, see Chapter 4, Plans, in N1 Grid Service Provisioning System 5.0 Plan and Component Developer’s Guide.

The Solaris Package: Create Package Component link creates a component of type com.sun.solaris#Package. This component references a file system package. A file system package contains a directory or series of directories that contain the files and scripts necessary to install the package.

The Solaris Datastream Package: Create Datastream Package Component link creates a component of type com.sun.solaris#StreamPackage. This component references a datastream package. A datastream package is a package that has been converted from a file system package into one data stream. For more information about datastream packages, see the pkgtrans(1) man page.

The Package components and the Datastream Package components contain the same component variables and component procedures. The variables and procedures are described below.

Component Variables

installName

The name to use for the package when it is installed. The default value is the name of the package component.

installPath

The path on the target host where the package will be downloaded.

installRoot

The path on the target host where the package will be installed.

pkgName

The name of the package.

When installing a datastream package, you might need to change the value of this variable. When installing a datastream package using the pkgadd command, you are prompted to enter the package name. The provisioning system cannot prompt you during the package installation for the package name, so you must supply the actual package name here.

You can find the package name for the datastream package in the header of the datastream file. In the following example, the package name is SMCcvs.

% head cvs-1.11.17-sol9-sparc-local
# PaCkAgE DaTaStReAm
SMCcvs 1 16852
# end of header
NAME=cvs
ARCH=sparc
VERSION=1.11.17
CATEGORY=application
VENDOR=Joe Smith et al
EMAIL=joe@smith.work.net
PSTAMP=Bob Miller

verboseMode

This variable enables you to supply the -v option to pkgadd(1M) when the package is added to the target host. The -v option traces all of the scripts that pkgadd executes, located in the pkginst/install directory. Use this option for debugging the procedural and non-procedural scripts. Valid values are true and false.

The remaining component variables correspond directly to the variable values that the provisioning system sets in an administration file that will be used to install the package. The provisioning system creates an administration file to provide information to the pkgadd command about how the installation should proceed. For more information about administration files, see Using an Administration File in System Administration Guide: Basic Administration. For descriptions of the following variables and valid values for each variable, see the admin(4) man page.

mail
instance
partial
runlevel
independ
redepend
space
setuid
conflict
action
basedir

Note –

The values set by the provisioning system for the administration file variables do not match the default values that are set in the administration file that is installed with the Solaris OS in the /var/sadm/install/admin directory. The values set by the provisioning system enable the package installation to complete without any interaction. For more information about the default values that are set in the administration file that is installed with the Solaris OS, see the admin(4) man page.

Component Procedures

default: install: Use this procedure to install a package on a target system or systems.
mark Only: install: If you manually installed a package on a target system or systems but want the provisioning system database to be aware that the package is installed on those systems, use this procedure.
default: uninstall: Use this procedure to uninstall a package from a target system or systems.
markOnly: uninstall: If you manually uninstalled a package from a target system or systems but want the provisioning system database to be aware that the package has been uninstalled from those systems, use this procedure.