[Go to CFHT Home Page] Man Pages
Back to Software Index  BORDER=0Manpage Top Level
    pkgparam(1) manual page Table of Contents

Name

pkgparam - displays package parameter values

Synopsis

pkgparam [ -v ] [ -R root_path ] [ -d device ] pkginst [ param ...]
pkgparam -f filename [ -v ] [ param ...]

Availability

SUNWcsu

Description

pkgparam displays the value associated with the parameter or parameters requested on the command line. The values are located in either the pkginfo file for pkginst or from the specific file named with the -f option.

One parameter value is shown per line. Only the value of a parameter is given unless the -v option is used. With this option, the output of the command is in this format:


parameter1=’value1’
parameter2=’value2’
parameter3=’value3’

If no parameters are specified on the command line, values for all parameters associated with the package are shown.

Options

Options and arguments for this command are:

-v
Verbose mode. Display name of parameter and its value.
-R root_path
Defines the full path name of a subdirectory to use as the root_path. All files, including package system information files, are relocated to a directory tree starting in the specified root_path.
-d device
Specify the device on which a pkginst is stored. It can be a directory pathname or the identifiers for tape, floppy disk or removable disk (for example, /var/tmp, /dev/diskette, and /dev/dsk/c1d0s0). The special token spool may be used to represent the default installation spool directory (/var/spool/pkg).
-f filename
Read filename for parameter values.
pkginst
Defines a specific package instance for which parameter values should be displayed.
param
Defines a specific parameter whose value should be displayed.

Errors

If parameter information is not available for the indicated package, the command exits with a non-zero status.

See Also

pkgtrans(1) , pkgmk(1) , pkgparam(1) , pkgproto(1)

Notes

The -f synopsis allows you to specify the file from which parameter values should be extracted. This file should be in the same format as a pkginfo file. As an example, such a file might be created during package development and used while testing software during this stage.


Table of Contents