svn commit: r40787 - head/en_US.ISO8859-1/books/handbook/cutting-edge
Warren Block
wblock at FreeBSD.org
Mon Jan 28 16:40:41 UTC 2013
Author: wblock
Date: Mon Jan 28 16:40:40 2013
New Revision: 40787
URL: http://svnweb.freebsd.org/changeset/doc/40787
Log:
CVS is going away soon. Suggesting it for ports, -STABLE, or -CURRENT,
even with a deprecation warning, is a disservice to new users.
This change removes cvsup, csup, and CVS references. SVN URLs are also
changed to the preferred form and links to the SVN mirrors are added.
Reviewed by: -doc mailing list
Modified:
head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Mon Jan 28 15:54:22 2013 (r40786)
+++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Mon Jan 28 16:40:40 2013 (r40787)
@@ -70,9 +70,7 @@
<listitem>
<para>How to keep your system up to date with
<application>freebsd-update</application>,
- <application>Subversion</application>,
- <application>CVSup</application>,
- <application>CVS</application>, or
+ <application>Subversion</application>, or
<application>CTM</application>.</para>
</listitem>
@@ -910,10 +908,14 @@ Fetching 133 new ports or files... done.
<title>Updating the Documentation Sources</title>
<para>The <application>Subversion</application> program can
- fetch a clean copy of the documentation sources by
- typing:</para>
+ fetch a clean copy of the documentation sources from the
+ western US mirror using the HTTPS protocol with this
+ command:</para>
- <screen>&prompt.root; <userinput>svn checkout <literal>svn://svn.FreeBSD.org/doc/head</literal> <filename class="directory">/usr/doc</filename></userinput></screen>
+ <screen>&prompt.root; <userinput>svn checkout <literal>https://svn0.us-west.FreeBSD.org/doc/head</literal> /usr/doc</userinput></screen>
+
+ <para>Please use the closest mirror from the available <link
+ linkend="svn-mirrors">Subversion mirror sites</link>.</para>
<para>The initial download of the documentation sources may take
a while. Let it run until it completes.</para>
@@ -1480,76 +1482,43 @@ Fetching 133 new ports or files... done.
<listitem>
<para>Grab the sources from a &os;
<link linkend="mirrors">mirror site</link>. You can do
- this in one of three ways:</para>
+ this in one of several ways:</para>
<orderedlist>
<indexterm>
<primary><command>svn</command></primary>
</indexterm>
<indexterm>
- <primary><command>cvsup</command></primary>
+ <primary><command>cron</command></primary>
</indexterm>
<indexterm>
- <primary><command>cron</command></primary>
+ <primary>-CURRENT</primary>
+ <secondary>Syncing with
+ <application>Subversion</application>
+ </secondary>
</indexterm>
<indexterm>
<primary>-CURRENT</primary>
<secondary>Syncing with
- <application>CVSup</application>
+ <application>CTM</application>
</secondary>
</indexterm>
<listitem>
- <para>Use the <link linkend="svn">svn</link> program
- to check out the desired development or release
- branch. This is the recommended method, providing
- access to &os; development as it occurs. The
- preferred URL prefix for
- <application>Subversion</application> checkout of
- the -CURRENT base system is
-
-<literal>http://svn.freebsd.org/base/head/</literal>;
- because of the size of the repository, it is
+ <para>Use the <link linkend="svn">svn</link> program to
+ check out the desired development or release branch.
+ This is the recommended method, providing access to
+ &os; development as it occurs. Checkout the
+ -CURRENT code from the <literal>head</literal>
+ branch of one of the <link
+ linkend="svn-mirrors">Subversion mirror
+ sites</link>.
+ Because of the size of the repository, it is
recommended that only desired subtrees be checked
out.</para>
</listitem>
<listitem>
- <para>Use the <link linkend="cvsup">cvsup</link>
- program with the <filename>supfile</filename> named
- <filename>standard-supfile</filename> available from
- <filename>/usr/share/examples/cvsup</filename>.
- You have to customize the sample
- <filename>supfile</filename> above, and configure
- <link linkend="cvsup">cvsup</link> for your
- environment.</para>
-
- <warning>
- <para><command>cvsup</command> has been deprecated
- by the Project, and is not recommended.</para>
- </warning>
-
- <note>
- <para>The sample
- <filename>standard-supfile</filename> is intended
- for tracking a specific security branch of &os;,
- and not &os.current;. You will need to edit this
- file and replace the following line:</para>
-
- <programlisting>*default release=cvs tag=RELENG_<replaceable>X</replaceable>_<replaceable>Y</replaceable></programlisting>
-
- <para>With this one:</para>
-
- <programlisting>*default release=cvs tag=.</programlisting>
-
- <para>For a detailed explanation of usable tags,
- please refer to the Handbook's
- <link linkend="cvs-tags">CVS Tags</link>
- section.</para>
- </note>
- </listitem>
-
- <listitem>
<indexterm>
<primary>-CURRENT</primary>
<secondary>Syncing with CTM</secondary>
@@ -1718,18 +1687,15 @@ Fetching 133 new ports or files... done.
<para>If you are already running a previous release of
&os; and wish to upgrade via sources then you can easily
- do so from &os;
+ do so from a &os;
<link linkend="mirrors">mirror site</link>. This can be
- done in one of three ways:</para>
+ done in one of several ways:</para>
<orderedlist>
<indexterm>
<primary><command>svn</command></primary>
</indexterm>
<indexterm>
- <primary><command>cvsup</command></primary>
- </indexterm>
- <indexterm>
<primary><command>cron</command></primary>
</indexterm>
<indexterm>
@@ -1748,33 +1714,17 @@ Fetching 133 new ports or files... done.
<ulink url="&url.base;/releng/">the release
engineering page</ulink>, such as
<literal>stable/9</literal> or
- <literal>releng/9.0</literal>. The preferred URL
- prefix for <application>Subversion</application>
- checkout of the base system is
- <literal>http://svn.freebsd.org/base/</literal>;
- because of the size of the repository, it is
+ <literal>releng/9.0</literal>. URL
+ prefixes for <application>Subversion</application>
+ checkout of the base system are shown in <link
+ linkend="svn-mirrors">Subversion mirror
+ sites</link>.
+ Because of the size of the repository, it is
recommended that only desired subtrees be checked
out.</para>
</listitem>
<listitem>
- <para>Use the <link linkend="cvsup">cvsup</link>
- program with the <filename>supfile</filename> named
- <filename>stable-supfile</filename> from the
- directory
- <filename>/usr/share/examples/cvsup</filename>.
- You have to customize the
- sample <filename>supfile</filename> above, and
- configure <link linkend="cvsup">cvsup</link> for
- your environment.</para>
-
- <warning>
- <para><command>cvsup</command> has been deprecated
- by the Project, and is not recommended.</para>
- </warning>
- </listitem>
-
- <listitem>
<indexterm>
<primary>-STABLE</primary>
<secondary>syncing with CTM</secondary>
@@ -1792,8 +1742,7 @@ Fetching 133 new ports or files... done.
<listitem>
<para>Essentially, if you need rapid on-demand access to
the source and communications bandwidth is not a
- consideration, use <command>cvsup</command> or
- <command>ftp</command>. Otherwise, use
+ consideration, use <application>Subversion</application>. Otherwise, use
<application>CTM</application>.</para>
</listitem>
@@ -1826,9 +1775,7 @@ Fetching 133 new ports or files... done.
connection to stay up-to-date with any given area of the &os;
project sources, or all areas, depending on what interests you.
The primary services we offer are
- <link linkend="svn">Subversion</link>,
- <link linkend="anoncvs">Anonymous CVS</link>,
- <link linkend="cvsup">CVSup</link>, and
+ <link linkend="svn">Subversion</link> and
<link linkend="ctm">CTM</link>.</para>
<warning>
@@ -1844,29 +1791,20 @@ Fetching 133 new ports or files... done.
</warning>
<indexterm>
- <primary>CVS</primary>
- <secondary>anonymous</secondary>
+ <primary>Subversion</primary>
</indexterm>
- <para><application>Subversion</application>,
- <application>Anonymous CVS</application> and
- <application>CVSup</application> use the
- <emphasis>pull</emphasis> model of updating sources. For
- <application>Subversion</application>, the user (or a
- <command>cron</command> script) invokes the
+ <para><application>Subversion</application> uses the
+ <emphasis>pull</emphasis> model of updating sources.
+ The user (or a <command>cron</command> script) invokes the
<command>svn</command> program, and it brings files up-to-date.
<application>Subversion</application> is the preferred means of
- updating local source trees. <command>cvsup</command> and
- <command>cvs</command> work under similar principles, but are
- now deprecated in favour of Subversion. The updates you receive
- are up-to-the-minute and you get them when, and only when, you
- want them. You can easily restrict your updates to the specific
- files or directories that are of interest to you. Updates are
- generated on the fly by the server, according to what you have
- and what you want to have. Unless the reason is truly
- compelling, <application>Subversion</application> should be used
- in preference to other synchronization mechanisms, which have
- been deprecated and will be discontinued in the future.</para>
+ updating local source trees.
+ The updates you receive are up-to-the-minute and
+ you get them when, and only when, you want them. You can easily
+ restrict your updates to the specific files or directories that
+ are of interest to you. Updates are generated on the fly by the
+ server, according to what you have and what you want to have.</para>
<indexterm>
<primary><application>CTM</application></primary>
@@ -1883,21 +1821,19 @@ Fetching 133 new ports or files... done.
&man.ctm.rmail.1; utility which will automatically decode,
verify and apply the changes to the user's copy of the sources.
This process is far more efficient than
- <application>CVSup</application>, and places less strain on our
+ <application>Subversion</application>, and places less strain on our
server resources since it is a <emphasis>push</emphasis> rather
than a <emphasis>pull</emphasis> model.</para>
<para>There are other trade-offs, of course. If you inadvertently
wipe out portions of your archive,
- <application>CVSup</application> will detect and rebuild the
+ <application>Subversion</application> will detect and rebuild the
damaged portions for you. <application>CTM</application> will
not do this, and if you wipe some portion of your source tree
out (and do not have it backed up) then you will have to start
- from scratch (from the most recent CVS
+ from scratch (from the most recent CTM
<quote>base delta</quote>) and rebuild it all with
- <application>CTM</application> or, with
- <application>Anonymous CVS</application>, simply delete the bad
- bits and resync.</para>
+ <application>CTM</application>.</para>
</sect1>
<sect1 id="makeworld">
@@ -2954,7 +2890,7 @@ Script done, …</screen>
<answer>
<para>There is no easy answer to this one, as it depends
on the nature of the change. For example, if you just
- ran <application>CVSup</application>, and it has shown
+ ran <application>Subversion</application>, and it has shown
the following files as being updated:</para>
<screen><filename>src/games/cribbage/instr.c</filename>
More information about the svn-doc-all
mailing list