- Separate a large <note> section into two.

- Add a <tip>, mentioning it might be desired to run make(1) multiple
  times when using the 'configure-recursive' target. [1]

Suggested by:	bjk [1]

1 files changed, 14 insertions, 0 deletions

diff --git a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml
index db2d5cf289..c6df8fb536 100644
--- a/en_US.ISO8859-1/books/handbook/ports/chapter.sgml
+++ b/en_US.ISO8859-1/books/handbook/ports/chapter.sgml
@@ -976,7 +976,9 @@ docbook                     =
 	    <command>make <maketarget>install</maketarget></command> and
 	    <command>make <maketarget>clean</maketarget></command>
 	    as three separate steps.</para>
+	</note>
 
+	<note>
 	  <para>When installing a port, using only <command>make
 	      <maketarget>install</maketarget></command> from the
 	    beginning means there will potentially be many waiting
@@ -990,6 +992,18 @@ docbook                     =
 	      [clean]</maketarget></command> afterwards.</para>
 	</note>
 
+	<tip>
+	  <para>When using <maketarget>config-recursive</maketarget>,
+	    the list of ports to configure are gathered by the
+	    <maketarget>all-depends-list</maketarget> &man.make.1;
+	    target.  It is often recommended to run <command>make
+	      <maketarget>config-recursive</maketarget></command>
+	    until all dependent ports options have been defined, and
+	    ports options &man.dialog.1; screens no longer
+	    appear, to be certain all ports options have been
+	    configured as intended.</para>
+	</tip>
+
 	<note>
 	  <para>Some shells keep a cache of the commands that are
 	    available in the directories listed in the