Home
Search all pages
Subjects
By activity
Professions, Sciences, Humanities, Business, ...
User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Text Strings
Conversions, tests, processing, manipulation,...
Math
Integer, Floating point, Matrix, Statistics, Boolean, ...
Processing
Algorithms, Memory, Process control, Debugging, ...
Stored Data
Data storage, Integrity, Encryption, Compression, ...
Communications
Networks, protocols, Interprocess, Remote, Client Server, ...
Hard World Timing, Calendar and Clock, Audio, Video, Printer, Controls...
File System
Management, Filtering, File & Directory access, Viewers, ...
|
|
|
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
PKG_INFO(1) OpenBSD Reference Manual PKG_INFO(1)
NAME
pkg_info - a utility for displaying information on software packages
SYNOPSIS
pkg_info [-cDdfIikLmpqRrvh] [-e package] [-l prefix] pkg-name [...]
pkg_info [-a flags]
DESCRIPTION
The pkg_info command is used to dump out information for packages, which
may be either packed up in files or already installed on the system with
the pkg_create(1) command.
The pkg-name may be the name of an installed package, the pathname to a
package distribution file, or a URL to an ftp-available package. pkg_in-
fo will try to complete pkg-name with a version number while looking
through installed packages.
The following command-line options are supported:
-a Show information for all currently installed packages.
-c Show the one-line comment field for each package.
-D Show the install-message file (if any) for each package.
-d Show the long-description field for each package.
-e pkg-name
This option allows you to test for the presence of another (per-
haps prerequisite) package from a script. If the package identi-
fied by pkg-name is currently installed, return 0, otherwise re-
turn 1. In addition, the names of any package(s) found installed
are printed to stdout unless turned off using the -q option.
If the given pkg-name contains a shell meta-character, it will be
matched against all installed packages using fnmatch(3). csh(1)
style ``{,}'' alternates have also been implemented in addition
to this. Package version numbers can also be matched in a rela-
tional manner using the ``>='', ``<='', ``>'', and ``<'' opera-
tors. For example, pkg_info -e 'name>=1.3' will match versions
1.3 and later of the name package.
-f Show the packing list instructions for each package.
-I Show the index entry for each package.
-i Show the install script (if any) for each package.
-k Show the de-install script (if any) for each package.
-L Show the files within each package. This is different from just
viewing the packing list, since full pathnames for everything are
generated.
-l str Prefix each information category header (see -q) shown with str.
This is primarily of use to front-end programs that want to re-
quest a lot of different information fields at once for a pack-
age, but don't necessary want the output intermingled in such a
way that they can't organize it. This lets you add a special to-
ken to the start of each field.
-m Show the mtree file (if any) for each package.
-p Show the installation prefix for each package.
-q Be ``quiet'' in emitting report headers and such, just dump the
raw info (basically, assume a non-human reading).
-R Show which packages are required by each package.
-r Show the requirements script (if any) for each package.
-v Turn on verbose output.
ENVIRONMENT
PKG_DBDIR The standard package database directory, /var/db/pkg, can be
overridden by specifying an alternative directory in the
PKG_DBDIR environment variable.
PKG_PATH This can be used to specify a colon-separated list of paths to
search for package files. The current directory is always
searched first, even if PKG_PATH is set. If PKG_PATH is used,
the suffix ``.tgz'' is automatically appended to the pkg-name,
whereas searching in the current directory uses pkg-name lit-
erally.
PKG_TMPDIR, TMPDIR
These are tried in turn (if set) as candidate directories in
which to create a ``staging area'' for any files extracted by
pkg_info from package files. If neither PKG_TMPDIR nor TMPDIR
yields a suitable scratch directory, /var/tmp, /tmp, and
/usr/tmp are tried in turn. Note that /usr/tmp may be creat-
ed, if it doesn't already exist.
Since pkg_info requires very little information to be extract-
ed from any package files examined, it is unlikely that these
environment variables would ever need to be used to work
around limited available space in the default locations.
TECHNICAL DETAILS
Package info is either extracted from package files named on the command
line, or from already installed package information in /var/db/pkg/<pkg-
name>.
SEE ALSO
pkg_add(1), pkg_create(1), pkg_delete(1), mktemp(3), mtree(8)
AUTHORS
Jordan Hubbard
most of the work
John Kohl
refined it for NetBSD
BUGS
Sure to be some.
OpenBSD 2.6 August 22, 1998 2
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts Institute of Technology, Free Software Foundation, FreeBSD Inc., and others. |
(Corrections, notes, and links courtesy of RocketAware.com)
FreeBSD Sources for pkg_info(1) OpenBSD sources for pkg_info(1)
Up to: File and Version Management - RCS, CVS, distribution, etc.
Up to: Installed Software Administration - installation utilities, consistency and security checks, virus scanners
RocketLink!--> Man page versions:
OpenBSD
FreeBSD
NetBSD
Others
Rapid-Links:
Search | About | Comments | Submit Path: RocketAware >
pkg_info.1/
RocketAware.com is a service of Mib Software Copyright 1999, Forrest J. Cavalier III. All Rights Reserved. We welcome submissions and comments
|