- "portsnap extract" automatically creates ${PORTSDIR} since a while,
let's correct a note about that; - add some filename tags.
This commit is contained in:
parent
60031e2237
commit
1a465e8fd8
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=27563
1 changed files with 7 additions and 4 deletions
|
@ -2430,8 +2430,11 @@ doc/zh_*</screen>
|
|||
<note>
|
||||
<para>In the default installation
|
||||
<filename role="directory">/usr/ports</filename> is not
|
||||
created. It should be created before
|
||||
<command>portsnap</command> is used.</para>
|
||||
created. If you run &os; 6.0-RELEASE, it should be created before
|
||||
<command>portsnap</command> is used. On more recent
|
||||
versions of &os; or <application>Portsnap</application>
|
||||
port, this operation will be done automatically at first use
|
||||
of the <command>portsnap</command> command.<para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
||||
|
@ -2474,7 +2477,7 @@ doc/zh_*</screen>
|
|||
<command>cron</command> job, since it is liable to cause
|
||||
major problems if it happens to run at the same time as a port
|
||||
is being built or installed. However, it is safe to update
|
||||
the ports INDEX files, and this can be done by passing the
|
||||
the ports <filename>INDEX</filename> files, and this can be done by passing the
|
||||
<option>-I</option> flag to
|
||||
<command>portsnap</command>. (Obviously, if
|
||||
<command>portsnap -I update</command> is run from
|
||||
|
@ -2484,7 +2487,7 @@ doc/zh_*</screen>
|
|||
|
||||
<para>Adding the following line to <filename>/etc/crontab</filename>
|
||||
will cause <command>portsnap</command> to update its
|
||||
compressed snapshot and the INDEX files in
|
||||
compressed snapshot and the <filename>INDEX</filename> files in
|
||||
<filename>/usr/ports/</filename>, and will send an email if any
|
||||
installed ports are out of date:</para>
|
||||
|
||||
|
|
Loading…
Reference in a new issue