pkgadd(1M) RISC/os Reference Manual pkgadd(1M)
NAME
pkgadd - transfer software package to the system
SYNOPSIS
pkgadd [-d device] [-r response] [-n] [-a admin] [pkginst1
[pkginst2[ ...]]]
pkgadd -s spool [-d device] [pkginst1 [pkginst2[ ...]]]
DESCRIPTION
pkgadd transfers the contents of a software package from the
distribution medium or directory to install it onto the sys-
tem. Used without the -d option, pkgadd looks in the
default spool directory for the package (var/spool/pkg).
Used with the -s option, it reads the package to a spool
directory instead of installing it.
-d Installs or copies a package from device. device
can be a full path name to a directory or the
identifiers for tape, floppy disk or removable
disk (for example, /var/tmp, /dev/diskette, or
diskette1). It can also be the device alias.
-r Identifies a file or directory, response, which
contains output from a previous pkgask session.
This file supplies the interaction responses that
would be requested by the package in interactive
mode. response must be a full pathname.
-n Installation occurs in non-interactive mode. The
default mode is interactive.
-a Defines an installation administration file,
admin, to be used in place of the default adminis-
tration file. The token none overrides the use of
any admin file, and thus forces interaction with
the user. Unless a full path name is given,
pkgadd looks in the var/sadm/install/admin direc-
tory for the file.
pkginst Specifies the package instance or list of
instances to be installed. The token all may be
used to refer to all packages available on the
source medium. The format pkginst.* can be used
to indicate all instances of a package.
-s Reads the package into the directory spool instead
of installing it.
When executed without options, pkgadd users /var/spool/pkg
(the default spool directory).
Printed 11/19/92 Page 1
pkgadd(1M) RISC/os Reference Manual pkgadd(1M)
NOTES
When transferring a package to a spool directory, the -r,
-n, and -a options cannot be used.
The -r option can be used to indicate a directory name as
well as a filename. The directory can contain numerous
response files, each sharing the name of the package with
which it should be associated. This would be used, for
example, when adding multiple interactive packages with one
invocation of pkgadd. Each package would need a response
file. If you create response files with the same name as
the package (i.e. package1 and package2), then name the
directory in which these files reside after the -r.
The -n option will cause the installation to halt if any
interaction is needed to complete it.
Page 2 Printed 11/19/92