From owner-svn-doc-all@FreeBSD.ORG Mon Jan 28 16:40:41 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1A31E320; Mon, 28 Jan 2013 16:40:41 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 0B5FCA63; Mon, 28 Jan 2013 16:40:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0SGee4j038951; Mon, 28 Jan 2013 16:40:40 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0SGeeIO038950; Mon, 28 Jan 2013 16:40:40 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201301281640.r0SGeeIO038950@svn.freebsd.org> From: Warren Block Date: Mon, 28 Jan 2013 16:40:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40787 - head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 16:40:41 -0000 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 @@ How to keep your system up to date with freebsd-update, - Subversion, - CVSup, - CVS, or + Subversion, or CTM. @@ -910,10 +908,14 @@ Fetching 133 new ports or files... done. Updating the Documentation Sources The Subversion program can - fetch a clean copy of the documentation sources by - typing: + fetch a clean copy of the documentation sources from the + western US mirror using the HTTPS protocol with this + command: - &prompt.root; svn checkout svn://svn.FreeBSD.org/doc/head /usr/doc + &prompt.root; svn checkout https://svn0.us-west.FreeBSD.org/doc/head /usr/doc + + Please use the closest mirror from the available Subversion mirror sites. The initial download of the documentation sources may take a while. Let it run until it completes. @@ -1480,76 +1482,43 @@ Fetching 133 new ports or files... done. Grab the sources from a &os; mirror site. You can do - this in one of three ways: + this in one of several ways: svn - cvsup + cron - cron + -CURRENT + Syncing with + Subversion + -CURRENT Syncing with - CVSup + CTM - Use the svn 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 - Subversion checkout of - the -CURRENT base system is - -http://svn.freebsd.org/base/head/; - because of the size of the repository, it is + Use the svn 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 head + branch of one of the Subversion mirror + sites. + Because of the size of the repository, it is recommended that only desired subtrees be checked out. - Use the cvsup - program with the supfile named - standard-supfile available from - /usr/share/examples/cvsup. - You have to customize the sample - supfile above, and configure - cvsup for your - environment. - - - cvsup has been deprecated - by the Project, and is not recommended. - - - - The sample - standard-supfile 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: - - *default release=cvs tag=RELENG_X_Y - - With this one: - - *default release=cvs tag=. - - For a detailed explanation of usable tags, - please refer to the Handbook's - CVS Tags - section. - - - - -CURRENT Syncing with CTM @@ -1718,18 +1687,15 @@ Fetching 133 new ports or files... done. 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; mirror site. This can be - done in one of three ways: + done in one of several ways: svn - cvsup - - cron @@ -1748,33 +1714,17 @@ Fetching 133 new ports or files... done. the release engineering page, such as stable/9 or - releng/9.0. The preferred URL - prefix for Subversion - checkout of the base system is - http://svn.freebsd.org/base/; - because of the size of the repository, it is + releng/9.0. URL + prefixes for Subversion + checkout of the base system are shown in Subversion mirror + sites. + Because of the size of the repository, it is recommended that only desired subtrees be checked out. - Use the cvsup - program with the supfile named - stable-supfile from the - directory - /usr/share/examples/cvsup. - You have to customize the - sample supfile above, and - configure cvsup for - your environment. - - - cvsup has been deprecated - by the Project, and is not recommended. - - - - -STABLE syncing with CTM @@ -1792,8 +1742,7 @@ Fetching 133 new ports or files... done. Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a - consideration, use cvsup or - ftp. Otherwise, use + consideration, use Subversion. Otherwise, use CTM. @@ -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 - Subversion, - Anonymous CVS, - CVSup, and + Subversion and CTM. @@ -1844,29 +1791,20 @@ Fetching 133 new ports or files... done. - CVS - anonymous + Subversion - Subversion, - Anonymous CVS and - CVSup use the - pull model of updating sources. For - Subversion, the user (or a - cron script) invokes the + Subversion uses the + pull model of updating sources. + The user (or a cron script) invokes the svn program, and it brings files up-to-date. Subversion is the preferred means of - updating local source trees. cvsup and - cvs 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, Subversion should be used - in preference to other synchronization mechanisms, which have - been deprecated and will be discontinued in the future. + 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. CTM @@ -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 - CVSup, and places less strain on our + Subversion, and places less strain on our server resources since it is a push rather than a pull model. There are other trade-offs, of course. If you inadvertently wipe out portions of your archive, - CVSup will detect and rebuild the + Subversion will detect and rebuild the damaged portions for you. CTM 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 base delta) and rebuild it all with - CTM or, with - Anonymous CVS, simply delete the bad - bits and resync. + CTM. @@ -2954,7 +2890,7 @@ Script done, … There is no easy answer to this one, as it depends on the nature of the change. For example, if you just - ran CVSup, and it has shown + ran Subversion, and it has shown the following files as being updated: src/games/cribbage/instr.c