From cf339349d5a042155c7069b9064f4bc128ae1213 Mon Sep 17 00:00:00 2001 From: wiz Date: Mon, 18 Feb 2002 17:07:20 +0000 Subject: Grammar improvements. --- Packages.txt | 51 ++++++++++++++++++++++++++------------------------- 1 file changed, 26 insertions(+), 25 deletions(-) (limited to 'Packages.txt') diff --git a/Packages.txt b/Packages.txt index 9b39c2ad8ce..cd0e972d5de 100644 --- a/Packages.txt +++ b/Packages.txt @@ -1,4 +1,4 @@ -# $NetBSD: Packages.txt,v 1.233 2002/02/18 16:40:34 seb Exp $ +# $NetBSD: Packages.txt,v 1.234 2002/02/18 17:07:20 wiz Exp $ ########################################################################### ========================== @@ -2172,47 +2172,48 @@ examples. =================================== Some packages install info files or use the makeinfo or install-info -commands. In such cases, the makefile fragment mk/texinfo.mk should be included -in the package Makefile before the inclusion of mk/bsd.pkg.mk. +commands. In such cases, the makefile fragment mk/texinfo.mk should be +included in the package Makefile before the inclusion of mk/bsd.pkg.mk. Newer versions of texinfo (version 4 and above) are, unfortunately, -incompatible, at the command line level, from previous versions and some +incompatible from previous versions at the command line level and some extensions were introduced in the TeXinfo macro set. So the package creator -should ensure that the correct binaries are selected, rather than relying on -the contents of the PATH variable in the shell. +should ensure that the correct binaries are selected, rather than relying +on the contents of the PATH variable in the shell. -The main info directory file needs to be updated to reflect the installation -of the info files. Some package's installation process take care of this -for you. Otherwise the NetBSD Packages Collection has an INFO_FILES +The main info directory file needs to be updated to reflect the +installation of info files. Some packages' installation processes take care +of this for you. Otherwise the NetBSD Packages Collection has an INFO_FILES definition which can be used to do this. Simply use the INFO_FILES= ident.info -definition in the package Makefile, where "ident.info" is the name of the info -file which installs an info dir entry. +definition in the package Makefile, where "ident.info" is the name of the +info file which installs an info dir entry. -A package creator should also take care that the package build and -install process uses correct version of the makeinfo and install-info commands. -Some Makefiles and configure scripts from recent software packages include the -pathnames to the makeinfo and install-info commands. Unfortunately, older -software packages tend not to do this, and, should this be the case, further -action is required of the package creator. +A package creator should also take care that the package build and install +process uses the correct version of the makeinfo and install-info commands. +Some Makefiles and configure scripts from recent software packages include +the pathnames to the makeinfo and install-info commands. Unfortunately, +older software packages tend not to do this, and, should this be the case, +further action is required of the package creator. -The mk/texinfo.mk makefile fragment will ensure that proper makeinfo and -install-info commands are available on the system as well as help to the +The mk/texinfo.mk makefile fragment will ensure that the proper makeinfo +and install-info commands are available on the system as well as help the configure and build process of the package to use known binaries for these commands. -If a minimum version of makeinfo and install-info commands are required +If a minimum version of makeinfo and install-info commands are required, define TEXINFO_REQD in the package's Makefile to this mininum version. -If a package is not well behaved (i.e. it does not pick MAKEINFO or -INSTALL_INFO in the environment at configure or build time) you should -- whatever is more appropriate: +If a package is not well behaved (i.e., it does not pick MAKEINFO or +INSTALL_INFO in the environment at configure or build time) you should do +one of the following, whichever is more appropriate: a) patch the package files so MAKEINFO or INSTALL_INFO are picked from the environment at configure or build time and get used instead of relying on makeinfo or install-info being accessible in PATH; - b) put TEXINFO_OVERRIDE=YES in the package Makefile to let some - sed manipulation on some packages source files (see mk/texinfo.mk content). + b) put TEXINFO_OVERRIDE=YES in the package Makefile to let some sed + manipulation happen on some packages source files (see contents of + mk/texinfo.mk). 11 Submitting & Committing ========================== -- cgit v1.2.3