From ec51c1d99ccdfa875e6c7547ab14a1c4f4367c15 Mon Sep 17 00:00:00 2001
From: Mark Linimon <linimon@FreeBSD.org>
Date: Fri, 15 Jun 2007 07:37:34 +0000
Subject: [PATCH] Deprecate chroot(8) as a way of testing ports, in favor of
 installing a ports tinderbox.

Clarify that port updates should be via diff(1), not shar(1).

Cross-reference the Updating section of the Porter's Handbook.
---
 .../articles/contributing-ports/article.sgml  | 27 ++++++++++++++++---
 1 file changed, 23 insertions(+), 4 deletions(-)

diff --git a/en_US.ISO8859-1/articles/contributing-ports/article.sgml b/en_US.ISO8859-1/articles/contributing-ports/article.sgml
index 4257a4a312..f371041c61 100644
--- a/en_US.ISO8859-1/articles/contributing-ports/article.sgml
+++ b/en_US.ISO8859-1/articles/contributing-ports/article.sgml
@@ -329,10 +329,10 @@
 
 	      <listitem>
 		<para>Make sure your port's dependencies are complete.
-		  If you have the resources, a good way of doing this
-		  is building and testing the port
-		  &man.chroot.8;'ed inside a newly
-		  installed world.</para>
+		  The recommended way of doing this is by installing
+		  your own ports <application>tinderbox</application>.
+		  See <link linkend="resources">resources</link>
+		  for more information.</para>
 	      </listitem>
 
 	      <listitem>
@@ -370,6 +370,16 @@
 	      one.  Please refer to
 	      <ulink url="&url.articles.problem-reports;">Writing FreeBSD Problem Reports</ulink>
 	      for information on how to write a really good PR.</para>
+
+	    <note>
+	      <para>Please do not submit a &man.shar.1; archive of the
+		entire port; instead, use &man.diff.1; <literal>-r</literal>.
+		In this way, committers can much more easily see exactly
+		what changes are being made.  The Porter's Handbook
+		section on
+		<ulink url="&url.books.porters-handbook;/port-upgrading.html">Upgrading</ulink>
+		has more information.</para>
+	    </note>
 	  </step>
 
 	  <step>
@@ -776,6 +786,15 @@
       <makevar>MASTER_SITES</makevar> updated.
     </para>
 
+    <para>The ports <application>tinderbox</application> is the most
+      thorough way to test a port through the entire cycle of installation,
+      packaging, and deinstallation.  It features a command-line
+      interface but also can be controlled via a web interface.
+      Please see <filename>ports/ports-mgmt/tinderbox</filename>.
+      More documentation is located at the
+      <ulink url="http://tinderbox.marcuscom.com/">marcuscom tinderbox home page</ulink>.
+      </para>
+
     <para>&man.portlint.1; is an application which can be used to verify
       that your port conforms to many important stylistic and functional
       guidelines.  <application>portlint</application> is a simple