This is an initial whitespace cleanup commit, new content to follow.

Adding hard line breaks at the end of sentences.

Approved by:	rwatson (mentor)
This commit is contained in:
kensmith 2004-03-01 21:50:49 +00:00
parent af0c8ecd6c
commit f6d6565003

View File

@ -47,10 +47,12 @@ or other subtle
attacks from miscreants who create dangerous package files.
.Pp
You are advised to verify the competence and identity of those who
provide installable package files. For extra protection, use the
provide installable package files.
For extra protection, use the
.Fl M
flag to extract the package file, and inspect its contents and scripts to
ensure it poses no danger to your system's integrity. Pay particular
ensure it poses no danger to your system's integrity.
Pay particular
attention to any +INSTALL, +POST-INSTALL, +DEINSTALL, +POST-DEINSTALL,
+REQUIRE or +MTREE_DIRS files, and inspect the +CONTENTS file for
.Cm @cwd ,
@ -68,7 +70,8 @@ command to examine the package file.
The following command line arguments are supported:
.Bl -tag -width indent
.It Ar pkg-name Op Ar pkg-name ...
The named packages are installed. A package name of - will cause
The named packages are installed.
A package name of - will cause
.Nm
to read from stdin.
If the packages are not found in the current
@ -85,7 +88,8 @@ package, do not execute them.
Don't actually install a package, just report the steps that
would be taken if it was.
.It Fl R
Do not record the installation of a package. This means
Do not record the installation of a package.
This means
that you cannot deinstall it later, so only use this option if
you know what you are doing!
.It Fl r
@ -94,7 +98,8 @@ This will determine the appropriate
objformat and release and then fetch and install the package.
.It Fl f
Force installation to proceed even if prerequisite packages are not
installed or the requirements script fails. Although
installed or the requirements script fails.
Although
.Nm
will still try to find and auto-install missing prerequisite packages,
a failure to find one will not be fatal.
@ -103,12 +108,14 @@ Set
.Ar prefix
as the directory in which to extract files from a package.
If a package has set its default directory, it will be overridden
by this flag. Note that only the first
by this flag.
Note that only the first
.Cm @cwd
directive will be replaced, since
.Nm
has no way of knowing which directory settings are relative and
which are absolute. It is rare in any case to see more than one
which are absolute.
It is rare in any case to see more than one
directory transition made, but when such does happen and you wish
to have control over *all* directory transitions, then you
may then wish to look into the use of
@ -132,7 +139,8 @@ By default, this is the string
but it may be necessary to override it in the situation where
space in your
.Pa /var/tmp
directory is limited. Be sure to leave some number of `X' characters
directory is limited.
Be sure to leave some number of `X' characters
for
.Xr mktemp 3
to fill in with a unique ID.
@ -145,11 +153,13 @@ file installation; often this is
.It Fl M
Run in
.Cm MASTER
mode. This is a very specialized mode for running
mode.
This is a very specialized mode for running
.Nm
and is meant to be run in conjunction with
.Cm SLAVE
mode. When run in this mode,
mode.
When run in this mode,
.Nm
does no work beyond extracting the package into a temporary staging
area (see the
@ -165,15 +175,18 @@ before acting on its contents.
.It Fl S
Run in
.Cm SLAVE
mode. This is a very specialized mode for running
mode.
This is a very specialized mode for running
.Nm
and is meant to be run in conjunction with
.Cm MASTER
mode. When run in this mode,
mode.
When run in this mode,
.Nm
expects the release contents to be already extracted and waiting
in the staging area, the location of which is read as a string
from stdin. The complete packing list is also read from stdin,
from stdin.
The complete packing list is also read from stdin,
and the contents then acted on as normal.
.El
.Pp
@ -183,7 +196,8 @@ arguments may be specified, each being either a file containing the
package (these usually end with a
.Dq .tbz
suffix) or a
URL pointing at a file available on an ftp site. Thus you may
URL pointing at a file available on an ftp site.
Thus you may
extract files directly from their anonymous ftp locations (e.g.\&
.Nm
.Li ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/shells/bash-1.14.7.tbz ) .
@ -196,8 +210,10 @@ the variable
.Bf -emphasis
FTP_PASSIVE_MODE
.Ef
to some value in your environment. Otherwise, the more standard
ACTIVE mode may be used. If
to some value in your environment.
Otherwise, the more standard
ACTIVE mode may be used.
If
.Nm
consistently fails to fetch a package from a site known to work,
it may be because you have a firewall that demands the usage of
@ -379,7 +395,8 @@ All the scripts are called with the environment variable
.Ev PKG_PREFIX
set to the installation prefix (see the
.Fl p
option above). This allows a package author to write a script
option above).
This allows a package author to write a script
that reliably performs some action on the directory where the package
is installed, even if the user might change it with the
.Fl p
@ -388,8 +405,10 @@ flag to
.Sh ENVIRONMENT
The value of the
.Ev PKG_PATH
is used if a given package can't be found. The environment variable
should be a series of entries separated by colons. Each entry
is used if a given package can't be found.
The environment variable
should be a series of entries separated by colons.
Each entry
consists of a directory name.
The current directory may be indicated
implicitly by an empty directory name, or explicitly by a single