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

CVS is going away soon. Suggesting it for ports, -STABLE, or -CURRENT,

Browse source 
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
This commit is contained in:
Warren Block 2013-01-28 16:40:40 +00:00
parent d7ddc2ac15
commit 6fa4d6ceac
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=40787
1 changed files with 50 additions and 114 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

164
en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml
View file

@ -70,9 +70,7 @@
<listitem> <listitem>
<para>How to keep your system up to date with <para>How to keep your system up to date with
<application>freebsd-update</application>, <application>freebsd-update</application>,
<application>Subversion</application>, <application>Subversion</application>, or
<application>CVSup</application>,
<application>CVS</application>, or
<application>CTM</application>.</para> <application>CTM</application>.</para>
</listitem> </listitem>
@ -910,10 +908,14 @@ Fetching 133 new ports or files... done.</screen>
<title>Updating the Documentation Sources</title> <title>Updating the Documentation Sources</title>
<para>The <application>Subversion</application> program can <para>The <application>Subversion</application> program can
fetch a clean copy of the documentation sources by fetch a clean copy of the documentation sources from the
typing:</para> 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 <para>The initial download of the documentation sources may take
a while. Let it run until it completes.</para> a while. Let it run until it completes.</para>
@ -1480,75 +1482,42 @@ Fetching 133 new ports or files... done.</screen>
<listitem> <listitem>
<para>Grab the sources from a &os; <para>Grab the sources from a &os;
<link linkend="mirrors">mirror site</link>. You can do <link linkend="mirrors">mirror site</link>. You can do
this in one of three ways:</para> this in one of several ways:</para>
<orderedlist> <orderedlist>
<indexterm> <indexterm>
<primary><command>svn</command></primary> <primary><command>svn</command></primary>
</indexterm> </indexterm>
<indexterm>
<primary><command>cvsup</command></primary>
</indexterm>
<indexterm> <indexterm>
<primary><command>cron</command></primary> <primary><command>cron</command></primary>
</indexterm> </indexterm>
<indexterm> <indexterm>
<primary>-CURRENT</primary> <primary>-CURRENT</primary>
<secondary>Syncing with <secondary>Syncing with
<application>CVSup</application> <application>Subversion</application>
</secondary>
</indexterm>
<indexterm>
<primary>-CURRENT</primary>
<secondary>Syncing with
<application>CTM</application>
</secondary> </secondary>
</indexterm> </indexterm>
<listitem> <listitem>
<para>Use the <link linkend="svn">svn</link> program <para>Use the <link linkend="svn">svn</link> program to
to check out the desired development or release check out the desired development or release branch.
branch. This is the recommended method, providing This is the recommended method, providing access to
access to &os; development as it occurs. The &os; development as it occurs. Checkout the
preferred URL prefix for -CURRENT code from the <literal>head</literal>
<application>Subversion</application> checkout of branch of one of the <link
the -CURRENT base system is linkend="svn-mirrors">Subversion mirror
sites</link>.
<literal>http://svn.freebsd.org/base/head/</literal>; Because of the size of the repository, it is
because of the size of the repository, it is
recommended that only desired subtrees be checked recommended that only desired subtrees be checked
out.</para> out.</para>
</listitem> </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> <listitem>
<indexterm> <indexterm>
<primary>-CURRENT</primary> <primary>-CURRENT</primary>
@ -1718,17 +1687,14 @@ Fetching 133 new ports or files... done.</screen>
<para>If you are already running a previous release of <para>If you are already running a previous release of
&os; and wish to upgrade via sources then you can easily &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 <link linkend="mirrors">mirror site</link>. This can be
done in one of three ways:</para> done in one of several ways:</para>
<orderedlist> <orderedlist>
<indexterm> <indexterm>
<primary><command>svn</command></primary> <primary><command>svn</command></primary>
</indexterm> </indexterm>
<indexterm>
<primary><command>cvsup</command></primary>
</indexterm>
<indexterm> <indexterm>
<primary><command>cron</command></primary> <primary><command>cron</command></primary>
</indexterm> </indexterm>
@ -1748,32 +1714,16 @@ Fetching 133 new ports or files... done.</screen>
<ulink url="&url.base;/releng/">the release <ulink url="&url.base;/releng/">the release
engineering page</ulink>, such as engineering page</ulink>, such as
<literal>stable/9</literal> or <literal>stable/9</literal> or
<literal>releng/9.0</literal>. The preferred URL <literal>releng/9.0</literal>. URL
prefix for <application>Subversion</application> prefixes for <application>Subversion</application>
checkout of the base system is checkout of the base system are shown in <link
<literal>http://svn.freebsd.org/base/</literal>; linkend="svn-mirrors">Subversion mirror
because of the size of the repository, it is sites</link>.
Because of the size of the repository, it is
recommended that only desired subtrees be checked recommended that only desired subtrees be checked
out.</para> out.</para>
</listitem> </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> <listitem>
<indexterm> <indexterm>
<primary>-STABLE</primary> <primary>-STABLE</primary>
@ -1792,8 +1742,7 @@ Fetching 133 new ports or files... done.</screen>
<listitem> <listitem>
<para>Essentially, if you need rapid on-demand access to <para>Essentially, if you need rapid on-demand access to
the source and communications bandwidth is not a the source and communications bandwidth is not a
consideration, use <command>cvsup</command> or consideration, use <application>Subversion</application>. Otherwise, use
<command>ftp</command>. Otherwise, use
<application>CTM</application>.</para> <application>CTM</application>.</para>
</listitem> </listitem>
@ -1826,9 +1775,7 @@ Fetching 133 new ports or files... done.</screen>
connection to stay up-to-date with any given area of the &os; connection to stay up-to-date with any given area of the &os;
project sources, or all areas, depending on what interests you. project sources, or all areas, depending on what interests you.
The primary services we offer are The primary services we offer are
<link linkend="svn">Subversion</link>, <link linkend="svn">Subversion</link> and
<link linkend="anoncvs">Anonymous CVS</link>,
<link linkend="cvsup">CVSup</link>, and
<link linkend="ctm">CTM</link>.</para> <link linkend="ctm">CTM</link>.</para>
<warning> <warning>
@ -1844,29 +1791,20 @@ Fetching 133 new ports or files... done.</screen>
</warning> </warning>
<indexterm> <indexterm>
<primary>CVS</primary> <primary>Subversion</primary>
<secondary>anonymous</secondary>
</indexterm> </indexterm>
<para><application>Subversion</application>, <para><application>Subversion</application> uses the
<application>Anonymous CVS</application> and <emphasis>pull</emphasis> model of updating sources.
<application>CVSup</application> use the The user (or a <command>cron</command> script) invokes the
<emphasis>pull</emphasis> model of updating sources. For
<application>Subversion</application>, the user (or a
<command>cron</command> script) invokes the
<command>svn</command> program, and it brings files up-to-date. <command>svn</command> program, and it brings files up-to-date.
<application>Subversion</application> is the preferred means of <application>Subversion</application> is the preferred means of
updating local source trees. <command>cvsup</command> and updating local source trees.
<command>cvs</command> work under similar principles, but are The updates you receive are up-to-the-minute and
now deprecated in favour of Subversion. The updates you receive you get them when, and only when, you want them. You can easily
are up-to-the-minute and you get them when, and only when, you restrict your updates to the specific files or directories that
want them. You can easily restrict your updates to the specific are of interest to you. Updates are generated on the fly by the
files or directories that are of interest to you. Updates are server, according to what you have and what you want to have.</para>
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>
<indexterm> <indexterm>
<primary><application>CTM</application></primary> <primary><application>CTM</application></primary>
@ -1883,21 +1821,19 @@ Fetching 133 new ports or files... done.</screen>
&man.ctm.rmail.1; utility which will automatically decode, &man.ctm.rmail.1; utility which will automatically decode,
verify and apply the changes to the user's copy of the sources. verify and apply the changes to the user's copy of the sources.
This process is far more efficient than 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 server resources since it is a <emphasis>push</emphasis> rather
than a <emphasis>pull</emphasis> model.</para> than a <emphasis>pull</emphasis> model.</para>
<para>There are other trade-offs, of course. If you inadvertently <para>There are other trade-offs, of course. If you inadvertently
wipe out portions of your archive, 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 damaged portions for you. <application>CTM</application> will
not do this, and if you wipe some portion of your source tree 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 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 <quote>base delta</quote>) and rebuild it all with
<application>CTM</application> or, with <application>CTM</application>.</para>
<application>Anonymous CVS</application>, simply delete the bad
bits and resync.</para>
</sect1> </sect1>
<sect1 id="makeworld"> <sect1 id="makeworld">
@ -2954,7 +2890,7 @@ Script done, &hellip;</screen>
<answer> <answer>
<para>There is no easy answer to this one, as it depends <para>There is no easy answer to this one, as it depends
on the nature of the change. For example, if you just 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> the following files as being updated:</para>
<screen><filename>src/games/cribbage/instr.c</filename> <screen><filename>src/games/cribbage/instr.c</filename>