The Portsnap port' or just Portsnap' is better than `Portsnap port' here.
Also add a '\'' in `the ports INDEX files', while I'm here.
This commit is contained in:
parent
632a8bba0f
commit
57df1a41a3
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=27594
1 changed files with 3 additions and 3 deletions
|
|
@ -2432,8 +2432,8 @@ doc/zh_*</screen>
|
|||
<filename role="directory">/usr/ports</filename> is not
|
||||
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
|
||||
versions of &os; or <application>Portsnap</application>,
|
||||
this operation will be done automatically at first use
|
||||
of the <command>portsnap</command> command.<para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
|
@ -2477,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 <filename>INDEX</filename> 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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue