2 .\" FreeBSD install - a package for the installation and maintenance
3 .\" of non-core utilities.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
18 .\" $FreeBSD: src/usr.sbin/pkg_install/info/pkg_info.1,v 1.24.2.13 2002/08/02 11:09:05 sobomax Exp $
19 .\" $DragonFly: src/usr.sbin/pkg_install/info/Attic/pkg_info.1,v 1.2 2003/06/17 04:29:59 dillon Exp $
26 .Nd a utility for displaying information on software packages
29 .Op Fl cdDfgGiIkLmopqrRsvVx
46 command is used to dump out information for packages, either packed up in
49 command or already installed on the system
54 The following command line options are supported:
55 .Bl -tag -width indent
57 The named packages are described. A package name may either be the name of
58 an installed package, the pathname to a package distribution file or a
59 URL to an FTP available package.
61 Show all currently installed packages.
63 Turn on verbose output.
65 Show the installation prefix for each package.
69 in emitting report headers and such, just dump the
70 raw info (basically, assume a non-human reading).
72 Show the (one line) comment field for each package.
74 Show the long description field for each package.
76 Show the install-message file for each package.
78 Show the packing list instructions for each package.
80 Show files that don't match the recorded checksum.
82 Show the install script (if any) for each package.
84 Show an index line for each package. This option takes
85 precedence over all other package formatting options.
87 Show the de-install script (if any) for each package.
89 Show the requirements script (if any) for each package.
91 Show the list of installed packages which require each package.
93 Show the mtree file (if any) for each package.
95 Show the files within each package. This is different from just
96 viewing the packing list, since full pathnames for everything
99 Show the total size occupied by files installed within each package.
103 path recorded on package generation. This path
104 intended to give an idea as to where the underlying port, from which
105 package was generated, is located in the
107 .Em "Ports Collection" .
109 Do not try to expand shell glob patterns in the
111 when selecting packages to be displayed (by default
113 automatically expands shell glob patterns in the
118 argument show which package it belongs to. If the file is not in the
119 current directory, and does not have an absolute path, then the
126 argument list all packages having this origin.
130 as a regular expression and display information only for packages
131 whose names match that regular expression. Multiple regular
132 expressions could be provided, in that case
134 displays information about all packages that match at least one
135 regular expression from the list.
137 If the package identified by
139 is currently installed, return 0, otherwise return 1. This option
140 allows you to easily test for the presence of another (perhaps
141 prerequisite) package from a script.
143 Prefix each information category header (see
147 This is primarily of use to front-end programs who want to request a
148 lot of different information fields at once for a package, but don't
149 necessary want the output intermingled in such a way that they can't
150 organize it. This lets you add a special token to the start of
159 By default, this is the string
160 .Pa /tmp/instmp.XXXXXX ,
161 but it may be necessary to override it in the situation where
164 directory is limited. Be sure to leave some number of `X' characters
167 to fill in with a unique ID.
168 .Bd -ragged -offset indent -compact
169 Note: This should really not be necessary with
171 since very little information is extracted from each package
172 and one would have to have a very small
174 indeed to overflow it.
177 Show revision number of the packing list format.
179 .Sh TECHNICAL DETAILS
180 Package info is either extracted from package files named on the
181 command line, or from already installed package information
183 .Pa /var/db/pkg/ Ns Aq Ar pkg-name .
186 points to the directory where
188 creates its temporary files.
189 If this variable is not set,
191 is used. If both are unset, the builtin defaults are used.
194 specifies an alternative location for the installed package database.
196 .Bl -tag -width /var/db/pkg -compact
198 Used if the environment variables
202 are not set, or if the directories named have insufficient space.
206 does not exist or has insufficient space.
212 Default location of the installed package database.
224 .An John Kohl Aq jtk@rational.com