From 5f57ec7515fafa64bd48837816c600edfd0eb2cc Mon Sep 17 00:00:00 2001 From: Ceri Davies Date: Mon, 19 Jan 2004 00:15:45 +0000 Subject: [PATCH] More wordsmithing. Submitted by: linimon PR: docs/53424 --- .../books/porters-handbook/book.sgml | 27 ++++++++++++++----- 1 file changed, 20 insertions(+), 7 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml index 97e2f0540d..eaea24b66e 100644 --- a/en_US.ISO8859-1/books/porters-handbook/book.sgml +++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml @@ -16,6 +16,8 @@ %teams; %mailing-lists; + +%freebsd; ]> @@ -4573,7 +4575,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION} When you notice that a port is out of date compared to the latest version from the original authors, first make sure you have the latest port. You can find them in the - ports/ports-current directory of the FTP mirror + ports/ports-current directory of the &os; FTP mirror sites. You may also use CVSup to keep your whole ports collection up-to-date, as described in the Handbook. @@ -4581,16 +4583,27 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION} listed in the port's Makefile. That person may already be working on an upgrade, or have a reason to not upgrade the port right now (because of, for example, stability problems of the new - version). + version); you would not want to duplicate their work. Note that + unmaintained ports are listed with a maintainer of + ports@FreeBSD.org; mail to that address + probably will not help in this case. - If the maintainer asks you to do the upgrade or there is not any - such person to begin with, please make the upgrade and send the - recursive diff (either unified or context diff is fine, but port - committers appear to prefer unified diff more) of the new and old + If the maintainer asks you to do the upgrade or the maintainer + is ports@FreeBSD.org, + please make the upgrade and send the + recursive diff output + of the new and old ports directories to us (e.g., if your modified port directory is called superedit and the original is in our tree as superedit.bak, then send us the result of - diff -ruN superedit.bak superedit). Please examine + diff -ruN superedit.bak superedit). Either + unified or context diff is fine, but port committers generally + prefer unified diffs. Note the use of the -N + option—this is the accepted way to force diff to properly + deal with the case of new files being added or old files being + deleted. + + Please examine the output to make sure all the changes make sense. The best way to send us the diff is by including it via &man.send-pr.1; (category ports). If you are the maintainer for the port,