prt-get.8: cleaned up the discussion of --install-root
This commit is contained in:
parent
156a9452db
commit
b45d8d3ae3
|
@ -308,7 +308,7 @@ for the list command. Make sure you escape where needed
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B printf <format string1> [\-\-sort=<format string2>] [\-\-filter=<filter>]
|
.B printf <format string1> [\-\-sort=<format string2>] [\-\-filter=<filter>]
|
||||||
Print formated port list format string can contain variables, which
|
Print formatted port list format string can contain variables, which
|
||||||
are replaced like this:
|
are replaced like this:
|
||||||
.TP
|
.TP
|
||||||
\ \ \ \(bu
|
\ \ \ \(bu
|
||||||
|
@ -398,7 +398,7 @@ any other port currently installed. Output appears alphabetically separated by n
|
||||||
suitable for process substitution as shown in the
|
suitable for process substitution as shown in the
|
||||||
.B EXAMPLES
|
.B EXAMPLES
|
||||||
section below. Note that some core ports might be runtime
|
section below. Note that some core ports might be runtime
|
||||||
dependencies despite their absence in the "Depends on:" line; see Pkgfile(5)
|
dependencies despite their absence in the "Depends on:" line; see \fBPkgfile(5)\fP
|
||||||
for an explanation of this practice. Also remember that this operation does NOT account for soft
|
for an explanation of this practice. Also remember that this operation does NOT account for soft
|
||||||
(optional) dependencies. Removing a non-core package returned by this command might require a
|
(optional) dependencies. Removing a non-core package returned by this command might require a
|
||||||
rebuild of other packages; use revdep(1) to locate such breakage.
|
rebuild of other packages; use revdep(1) to locate such breakage.
|
||||||
|
@ -543,13 +543,14 @@ Use <dir> as root directory for your installation; allows you to install the req
|
||||||
onto a different directory than '/'. In daily usage, this option is not required; it's primarily
|
onto a different directory than '/'. In daily usage, this option is not required; it's primarily
|
||||||
interesting if you're developing an independent installation.
|
interesting if you're developing an independent installation.
|
||||||
|
|
||||||
Most of the commands fully respect the setting for --install-root, and behave as if you chrooted to
|
The setting for --install-root determines which package database is used for reading/writing (so
|
||||||
<dir> before running the command (except that the programs \fBprt\-get, pkgmk, pkgadd, pkgrm\fP
|
<dir>/var/lib/pkg/db must exist), and where the pkg.tar.?z archives get unpacked, but the
|
||||||
are those on the parent filesystem, not those under <dir>). This can lead to surprising side effects
|
relevant prt\-get.conf and ports tree are those on the parent filesystem. Therefore it is not
|
||||||
if, for example, /etc/pkgadd.conf has different directives than <dir>/etc/pkgadd.conf. In order to
|
necessary for <dir> to contain its own copy of the ports tree, or even a copy of prt-get.conf.
|
||||||
preserve the \fBpkgadd.conf(5)\fP settings from the host system, append the option --aargs='-c
|
However, if <dir>/etc/pkgadd.conf exists and is different from /etc/pkgadd.conf, then install or
|
||||||
/etc/pkgadd.conf' to your \fBprt-get install\fP command, or just copy the desired directives into
|
update commands might behave unexpectedly. In order to preserve the \fBpkgadd.conf(5)\fP settings
|
||||||
<dir>/etc/pkgadd.conf .
|
from the host system, append the option --aargs='-c /etc/pkgadd.conf' to your \fBprt-get install\fP
|
||||||
|
command, or just copy the desired directives into <dir>/etc/pkgadd.conf .
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.B \-\-log
|
.B \-\-log
|
||||||
|
|
Loading…
Reference in New Issue