Subject: pkg/20178: Packages.txt has some spelling/grammar errors
To: None <firstname.lastname@example.org>
From: None <email@example.com>
Date: 02/03/2003 03:33:55
>Synopsis: Packages.txt has some spelling/grammar errors
>Arrival-Date: Sun Feb 02 19:29:00 PST 2003
>Release: NetBSD 1.6M
System: NetBSD monstar 1.6M NetBSD 1.6M (MONSTAR) #0: Tue Jan 28 18:05:20 PST 2003 soren@monstar:/usr/src/sys/arch/i386/compile/MONSTAR i386
Apply the following patch.
RCS file: /cvsroot/pkgsrc/Packages.txt,v
retrieving revision 1.284
diff -u -r1.284 Packages.txt
--- Packages.txt 2003/01/29 08:50:11 1.284
+++ Packages.txt 2003/02/03 03:16:15
@@ -41,7 +41,7 @@
This document is divided into two parts. The first, "User's Guide",
describes how one can use one of the packages in the Package
Collection, either by installing a precompiled binary package, or
-by building your own copy using the NetBSD package system. The
+by building one's own copy using the NetBSD package system. The
second part, "Package Constructor's Guide", explains how to prepare
a package so it can be easily built by other NetBSD users without
knowing about the package's building details.
@@ -103,7 +103,7 @@
Right now this document is written in plain ASCII text, and there's not
much typography applied here. Future versions may move to something like
-HTML or DocBook, which have better ways theres.
+HTML or DocBook to improve this.
When giving examples for commands, shell prompts are used to show if the
command should/can be issued as root, or if "normal" user privileges are
@@ -574,7 +574,7 @@
This will just jump inside the sandbox and start thrash^Wbuilding.
At the end of the build, mail will be sent with the results of the build.
-Created binary pkgs will be in /usr/sandbox/usr/pkgsrc/packages (whereever
+Created binary pkgs will be in /usr/sandbox/usr/pkgsrc/packages (where ever
that points/mounts to/from).
@@ -606,7 +606,7 @@
contains these files. For example
# mkdir /tmp/common
- # echo "This is a README" > /tmp/commmon/README
+ # echo "This is a README" > /tmp/common/README
# echo "Another file" > /tmp/common/COPYING
# mkdir /tmp/common/bin
# echo "#!/bin/sh" > /tmp/common/bin/myscript
@@ -1566,8 +1566,8 @@
DEPENDS. Useful if out of date DEPENDS are causing build problems.
- After a package is installed, check all it's binaries and (on ELF
- platforms) shared libraries if they find the shared libs they need.
+ After a package is installed, check all its binaries and (on ELF
+ platforms) shared libraries to see if they find the shared libs they need.
Run by default if PKG_DEVELOPER is set in /etc/mk.conf.
@@ -1727,7 +1727,7 @@
* Edit the Makefile as requested.
* Fill in DESCR
* ``make configure''
- * Add any dependancies glimpsed from the configure step to the package's
+ * Add any dependencies glimpsed from the configure step to the package's
* Make the package compile, doing multiple rounds of
@@ -2000,10 +2000,10 @@
(c) If your package needs some executable to be able to run correctly, this
is specified using the DEPENDS definition. The pkgsrc/print/lyx package needs
-to be able to execute the latex binary from the teTex package when it runs,
+to be able to execute the latex binary from the teTeX package when it runs,
and that is specified:
- DEPENDS+= teTex-[0-9]*:../../print/teTeX
+ DEPENDS+= teTeX-[0-9]*:../../print/teTeX
The comment about wildcard dependencies from previous paragraph
applies here, too.
@@ -2269,7 +2269,7 @@
Some source files trigger bugs in the compiler, based on combinations
of compiler version and architecture and almost always relation to
-optimsation being enabled. Common symptoms are gcc internal errors
+optimisation being enabled. Common symptoms are gcc internal errors
or never finishing compiling a file.
Typically a workaround involves testing the MACHINE_ARCH and compiler
@@ -2313,7 +2313,7 @@
If a minimum version of makeinfo and install-info commands are required,
-define TEXINFO_REQD in the package's Makefile to this mininum version.
+define TEXINFO_REQD in the package's Makefile to this minimum 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 do