docs/90515: Use new patch naming convention in Porter's Handbook

[Gabor Kovesdan]

>Number:         90515
>Category:       docs
>Synopsis:       Use new patch naming convention in Porter's Handbook
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Fri Dec 16 20:30:03 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Gabor Kovesdan
>Release:        FreeBSD 5.3-RELEASE-p17 amd64
>Organization:
n/a
>Environment:
System: FreeBSD server.t-hosting.hu 5.3-RELEASE-p17 FreeBSD 5.3-RELEASE-p17 #0: Mon Jul 4 20:23:15 CEST 2005 root at server.t-hosting.hu:/usr/src/sys/amd64/compile/FREEBSD amd64

>Description:

According to http://wikitest.freebsd.org/moin.cgi/PortsLongtermTargets the new
patch naming convention requires to use :: signs for specifying paths in the
patch filenames, e.g. patch-src::config.c, but Porter's Handbook describes the
old naming convention, e.g. patch-src-config.c.
This patch updates Porter's Handbook to explain the new rule.


>How-To-Repeat:
>Fix:

--- book.sgml.diff begins here ---
--- /usr/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml	Thu Dec 15 09:49:06 2005
+++ ./book.sgml	Fri Dec 16 21:21:09 2005
@@ -635,11 +635,14 @@
 	  <replaceable>*</replaceable> indicates
 	  the pathnames of the files that are patched,
 	  such as <filename>patch-Imakefile</filename> or
-	  <filename>patch-src-config.h</filename>.  These files should
+	  <filename>patch-src::config.h</filename>. All patches must be
+	  relative to <makevar>WRKSRC</makevar> (generally the directory your
+	  port's tarball unpacks itself into, that being where the build is
+	  done), and the / signs must be substituted with :: in this relative
+	  path when constructing patch filenames, as the example represents
+	  above. The patch files should
 	  be stored in <makevar>PATCHDIR</makevar>, from where they will be
-	  automatically applied.  All patches must be relative to
-	  <makevar>WRKSRC</makevar> (generally the directory your port's
-	  tarball unpacks itself into, that being where the build is done).
+	  automatically applied.
 	  To make fixes and upgrades easier, you should avoid having more than
 	  one patch fix the same file (e.g., <filename>patch-file</filename> and
 	  <filename>patch-file2</filename> both changing
--- book.sgml.diff ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted: