os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Mention that svnlite may be present and usable. Adjust some wording to

Browse source 
try to not scare people away from using svn.  Mention the importance of
ca_root_nss and add it to the examples.  Use short package names in
examples.  Untangle some leftovers from having a mirror list.

Build tested by:  gjb
This commit is contained in:
Peter Wemm 2015-08-06 21:18:32 +00:00
parent db36ce3286
commit 7a5c6d7474
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=47170
1 changed files with 38 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

51
en_US.ISO8859-1/books/handbook/mirrors/chapter.xml
View file

@ -436,13 +436,13 @@ Comment out for now until these can be verified.
<title>Introduction</title>
<para>As of July 2012, &os; uses
<application>Subversion</application> as the primary version
<application>Subversion</application> as the only version
control system for storing all of &os;'s source code,
documentation, and the Ports Collection.</para>
<note>
<para><application>Subversion</application> is generally a
developer tool. Most users should use
developer tool. Users may prefer to use
<command>freebsd-update</command> (<xref
linkend="updating-upgrading-freebsdupdate"/>) to update
the &os; base system, and <command>portsnap</command> (<xref
@ -453,29 +453,54 @@ Comment out for now until these can be verified.
<para>This chapter demonstrates how to install
<application>Subversion</application> on a &os; system and
then use it to create a local copy of a &os; repository. It
includes a list of the available &os;
<application>Subversion</application> mirrors and resources to
additional information on how to use
includes additional information on how to use
<application>Subversion</application>.</para>
</sect2>
<sect2 xml:id="svn-svnlite">
<title>Svnlite</title>
<para>A fully functional but light weight version of
<application>Subversion</application> may be already installed
on your &os; system as <command>svnlite</command>. You do not
have to install a separate copy if <command>svnlite</command>
is sufficient for your needs.</para>
<para>If you wish to access <acronym>HTTPS</acronym> servers with
<command>svnlite</command> then a root certificate bundle
should be installed:</para>
<screen>&prompt.root; <userinput>pkg install ca_root_nss</userinput></screen>
<para>Installing a certificate bundle allows
<command>svnlite</command> to verify that it is securely
communicating with the repository server without tampering.</para>
<para>If you are using <command>svnlite</command> then you should
adjust the examples below.</para>
</sect2>
<sect2 xml:id="svn-install">
<title>Installation</title>
<para><application>Subversion</application> must be installed
before it can be used to check out the contents of any of the
repositories. If a copy of the ports tree is already present,
<para>If the <command>svnlite</command> is unavailable or you wish to
use the full version of <application>Subversion</application> then
it must be installed.</para>
<para>If a copy of the ports tree is already present,
one can install <application>Subversion</application> like
this:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/devel/subversion</userinput>
&prompt.root; <userinput>make install clean</userinput>
&prompt.root; <userinput>cd /usr/ports/security/ca_root_nss</userinput>
&prompt.root; <userinput>make install clean</userinput></screen>
<para>If the ports tree is not available,
<application>Subversion</application> can be installed as a
package:</para>
<para><application>Subversion</application> can easily be
installed as a package:</para>
<screen>&prompt.root; <userinput>pkg install devel/subversion</userinput></screen>
<screen>&prompt.root; <userinput>pkg install subversion</userinput>
&prompt.root; <userinput>pkg install ca_root_nss</userinput></screen>
</sect2>
<sect2 xml:id="svn-usage">
@ -561,7 +586,7 @@ Comment out for now until these can be verified.
</itemizedlist>
<para>This example checks out the Ports Collection from the
western US repository using the <acronym>HTTPS</acronym>
&os; repository using the <acronym>HTTPS</acronym>
protocol, placing the local working copy in
<filename>/usr/ports</filename>. If
<filename>/usr/ports</filename> is already