From 71dcef104348942a3d6e1330ca0b749aee24031c Mon Sep 17 00:00:00 2001 From: Thomas Abthorpe Date: Tue, 27 Jan 2009 16:05:37 +0000 Subject: [PATCH] - Clean up some grammar - Document ports-mgmt/genplist PR: docs/121197 Submitted by: Chess Griffin Reviewed by: pav Approved by: trhodes --- .../books/porters-handbook/book.sgml | 25 +++++++++++-------- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git a/en_US.ISO8859-1/books/porters-handbook/book.sgml b/en_US.ISO8859-1/books/porters-handbook/book.sgml index eee6b41384..b6c3020d92 100644 --- a/en_US.ISO8859-1/books/porters-handbook/book.sgml +++ b/en_US.ISO8859-1/books/porters-handbook/book.sgml @@ -2412,10 +2412,10 @@ EXTRACT_ONLY= source.tar.gz hereon. A little background first. OpenBSD has a neat feature - inside both DISTFILES and - PATCHFILES variables, both files and - patches can be postfixed with :n - identifiers where n both can be + inside the DISTFILES and + PATCHFILES variables which allows files and + patches to be postfixed with :n + identifiers. Here, n can be both [0-9] and denote a group designation. For example: @@ -2436,7 +2436,7 @@ EXTRACT_ONLY= source.tar.gz as hell where beta is carried by all sites in MASTER_SITES, and alpha can only be found in the 20th - site. It would be such a waste to check all of them if + site. It would be such a waste to check all of them if the maintainer knew this beforehand, would it not? Not a good start for that lovely weekend! @@ -3121,7 +3121,7 @@ ALWAYS_KEEP_DISTFILES= yes challenge for port maintainers section. Changes to the port will be sent to the maintainer of - a port for a review and an approval before being committed. + a port for review and approval before being committed. If the maintainer does not respond to an update request after two weeks (excluding major public holidays), then that is considered a maintainer timeout, and the @@ -3137,8 +3137,8 @@ ALWAYS_KEEP_DISTFILES= yes to better match existing policies and style of the Ports Collection without explicit blessing from the submitter. Also, large infrastructural changes can result in - a port being modified without maintainer's consent. - This kind of changes will never affect the port's + a port being modified without the maintainer's consent. + These kinds of changes will never affect the port's functionality. The &a.portmgr; reserves the right to revoke or override @@ -4090,7 +4090,7 @@ PORTVERSION= 1.0 Two macros exists for this situation. The advantage of using these macros instead of cp is that they guarantee - proper file ownership and permissions on target files. First macro, + proper file ownership and permissions on target files. The first macro, COPYTREE_BIN, will set all the installed files to be executable, thus being suitable for installing into PREFIX/bin. The second @@ -8645,6 +8645,11 @@ etc/orbit.conf.sample The packing list still has to be tidied up by hand as stated above. + Another tool that might be used to create an initial + pkg-plist is ports-mgmt/genplist. As with any + automated tool, the resulting pkg-plist + should be checked and manually edited as needed. @@ -11882,7 +11887,7 @@ Reference: <http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00 7.0-CURRENT after RFC 3678 API support added to the IPv4 stack. - Legacy RFC 1724 behaviour of the IP_MULTICAST_IF + Legacy RFC 1724 behavior of the IP_MULTICAST_IF ioctl has now been removed; 0.0.0.0/8 may no longer be used to specify an interface index. struct ipmreqn should be used instead.