From 3eb92fc0e4459b85310fa0d6f564938c64c93c0f Mon Sep 17 00:00:00 2001
From: Rong-En Fan <rafan@FreeBSD.org>
Date: Thu, 26 Jul 2007 15:30:18 +0000
Subject: [PATCH] - Expand INFO section a little bit

Reviewed by:	gerald
---
 .../books/porters-handbook/book.sgml          | 19 ++++++++++++++++---
 1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml
index 7d5419aece..002b56c35a 100644
--- a/en_US.ISO8859-1/books/porters-handbook/book.sgml
+++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml
@@ -3727,9 +3727,22 @@ ${MANPREFIX}/man/de/man3/baz.3.gz</programlisting>
 
       <para>If your package needs to install GNU info files, they should be
 	listed in the <makevar>INFO</makevar> variable (without the trailing
-	<literal>.info</literal>), and appropriate installation/de-installation
-	code will be automatically added to the temporary
-	<filename>pkg-plist</filename> before package registration.</para>
+	<literal>.info</literal>), one entry per document.  These files
+	are assumed to be installed to
+	<filename><makevar>PREFIX</makevar>/<makevar>INFO_PATH</makevar></filename>.
+	You can change <makevar>INFO_PATH</makevar> if your package uses
+	a different location.  However, this is not recommended.  These entries
+	contain just the path relative to
+	<filename><makevar>PREFIX</makevar>/<makevar>INFO_PATH</makevar></filename>.
+	For example, <filename role="package">lang/gcc33</filename> installs
+	info files to
+	<filename><makevar>PREFIX</makevar>/<makevar>INFO_PATH</makevar>/gcc33</filename>,
+	and <makevar>INFO</makevar> will be something like this:
+	<programlisting>INFO= gcc33/cpp gcc33/cppinternals gcc33/g77 ...
+</programlisting>
+	Appropriate installation/de-installation code will be automatically
+	added to the temporary <filename>pkg-plist</filename> before package
+	registration.</para>
     </sect1>
 
       <sect1 id="makefile-options">