svn commit: r40143 - head/en_US.ISO8859-1/articles/portbuild

[Mark Linimon]

Author: linimon
Date: Fri Nov 23 22:58:53 2012
New Revision: 40143
URL: http://svnweb.freebsd.org/changeset/doc/40143

Log:
  Note some more obsolete stuff, mostly having to do with cvs.

Modified:
  head/en_US.ISO8859-1/articles/portbuild/article.xml

Modified: head/en_US.ISO8859-1/articles/portbuild/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/portbuild/article.xml	Fri Nov 23 18:30:58 2012	(r40142)
+++ head/en_US.ISO8859-1/articles/portbuild/article.xml	Fri Nov 23 22:58:53 2012	(r40143)
@@ -1056,16 +1056,16 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5
       then <trademark>Bad Things</trademark> happen.
     </para>
 
-    <para>The status of all current builds is generated twice an hour
+    <para>The status of all current builds is generated periodically
       and posted to
       <ulink url="http://pointyhat.FreeBSD.org/errorlogs/packagestats.html"></ulink>.
       For each <literal>buildenv</literal>, the following is displayed:</para>
 
     <itemizedlist>
       <listitem>
-	<para><literal>cvs date</literal> is the contents of
-	  <filename>cvsdone</filename>.  This is why we recommend that you
-	  update <filename>cvsdone</filename> for <literal>-exp</literal>
+	<para><literal>updated</literal> is the contents of
+	  <filename>.updated</filename>.  This is why we recommend that you
+	  update <filename>.updated</filename> for <literal>-exp</literal>
 	  runs (see below).</para>
       </listitem>
 
@@ -1312,12 +1312,17 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5
     <para>In general, an experimental patches build is run the same
       way as any other build, except that you should first update the
       ports tree to the latest version and then apply your patches.
-      To do the former, you can use the following:
+      To do the former, you can use the following:</para>
 
+    <note>
+      <para>The following example is obsolete<para>
+    </note>
+
+    <para>
       <screen>&prompt.user; <userinput>cvs -R update -dP > update.out</userinput>
-&prompt.user; <userinput>date > cvsdone</userinput></screen>
+&prompt.user; <userinput>date > .updated</userinput></screen>
       This will most closely simulate what the <literal>dopackages</literal>
-      script does.  (While <filename>cvsdone</filename> is merely
+      script does.  (While <filename>.updated</filename> is merely
       informative, it can be a help.)</para>
 
     <para>You will need to edit <filename>update.out</filename> to look
@@ -1425,6 +1430,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/5
 
     <screen>&prompt.user; <userinput>cd /var/portbuild/i386/8/ports</userinput></screen>
 
+    <note>
+      <para>The following example is obsolete<para>
+    </note>
+
+    <para>
     <note><para>Be sure to <literal>cvs update</literal> this tree to the same date as
       the experimental patches tree.</para></note>
 
@@ -3242,6 +3252,11 @@ qmanager.sh</screen>
   <sect1 id="disk-failure">
     <title>Procedures for dealing with disk failures</title>
 
+    <note>
+      <para>The following section is particular to <hostid>freebsd.org</hostid>
+	and is somewhat obsolete.</para>
+    </note>
+
     <para>When a machine has a disk failure (e.g. panics due to read errors,
       etc), then we should do the following steps:</para>