Some spelling, grammar, and clarity fixes.

Approved by:	gjb (mentor)
This commit is contained in:
Warren Block 2012-01-03 01:31:44 +00:00
parent 61da3cf960
commit be328e477d
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=38125

View file

@ -460,7 +460,7 @@ PLIST_DIRS= lib/X11/oneko</programlisting>
<para>But do not worry if you do not really understand what
<filename>bsd.port.mk</filename> is doing, not many people
do... <!-- smiley --><emphasis>:-&gt;</emphasis></para>
do... <!-- smiley --><emphasis>:-)</emphasis></para>
<procedure>
<step>
@ -484,7 +484,7 @@ PLIST_DIRS= lib/X11/oneko</programlisting>
<step>
<para>The <maketarget>extract</maketarget> target is run.
It looks for your port's distribution file (typically a
gzip'd tarball) in <makevar>DISTDIR</makevar> and unpacks
<command>gzip</command>ped tarball) in <makevar>DISTDIR</makevar> and unpacks
it into a temporary subdirectory specified by
<makevar>WRKDIR</makevar> (defaults to
<filename>work</filename>).</para>
@ -842,7 +842,7 @@ DOS2UNIX_REGEX= .*\.(c|cpp|h)</programlisting>
<title>The original source</title>
<para>Does it live in <makevar>DISTDIR</makevar> as a standard
gzip'd tarball named something like
<command>gzip</command>ped tarball named something like
<filename>foozolix-1.2.tar.gz</filename>? If so, you can go on
to the next step. If not, you should look at overriding any
of the <makevar>DISTVERSION</makevar>,
@ -2443,7 +2443,7 @@ MASTER_SITE_SUBDIR= make</programlisting>
<programlisting>MASTER_SITES= SF</programlisting>
<para>If the guess is incorrect, it can be overriden as
<para>If the guess is incorrect, it can be overridden as
follows.</para>
<programlisting>MASTER_SITES= SF/stardict/WyabdcRealPeopleTTS/${PORTVERSION}</programlisting>
@ -2635,7 +2635,7 @@ EXTRACT_ONLY= source.tar.gz</programlisting>
<filename>.gz</filename> or <filename>.Z</filename>.</para>
<para>If the patch is distributed with some other files, such
as documentation, in a gzip'd tarball, you cannot just use
as documentation, in a <command>gzip</command>ped tarball, you cannot just use
<makevar>PATCHFILES</makevar>. If that is the case, add the
name and the location of the patch tarball to
<makevar>DISTFILES</makevar> and
@ -2650,7 +2650,7 @@ EXTRACT_ONLY= source.tar.gz</programlisting>
<note>
<para>The tarball will have been extracted alongside the
regular source by then, so there is no need to explicitly
extract it if it is a regular gzip'd or compress'd
extract it if it is a regular <command>gzip</command>ped or <command>compress</command>ed
tarball. If you do the latter, take extra care not to
overwrite something that already exists in that directory.
Also, do not forget to add a command to remove the copied
@ -2671,8 +2671,7 @@ EXTRACT_ONLY= source.tar.gz</programlisting>
<para>This section has information on the fetching mechanism
known as both <literal>MASTER_SITES:n</literal> and
<literal>MASTER_SITES_NN</literal>. We will refer to this
mechanism as <literal>MASTER_SITES:n</literal>
hereon.</para>
mechanism as <literal>MASTER_SITES:n</literal>.</para>
<para>A little background first. OpenBSD has a neat feature
inside the <makevar>DISTFILES</makevar> and
@ -3442,11 +3441,11 @@ ALWAYS_KEEP_DISTFILES= yes
<sect1 id="makefile-depend">
<title>Dependencies</title>
<para>Many ports depend on other ports. This is very convenient
and nice feature of most Unix-like operating systems,
including &os;. It allows not having to bundle common
dependencies with every port or package, since a lot of ports
would share them. There are seven variables that can be used
<para>Many ports depend on other ports. This is a very
convenient feature of most Unix-like operating systems,
including &os;. Multiple ports can share a common dependency,
rather than bundling that dependency with every port or
package that needs it. There are seven variables that can be used
to ensure that all the required bits will be on the user's
machine. There are also some pre-supported dependency
variables for common cases, plus a few more to control the
@ -4463,7 +4462,7 @@ PORTVERSION= 1.0</programlisting>
<listitem>
<para><makevar>INSTALL_KLD</makevar> is a command to
install kernel loadable modules. Some architectures
don't like it when the modules are stripped, therefor
do not like having the modules stripped, so
use this command instead of
<makevar>INSTALL_PROGRAM</makevar>.</para>
</listitem>
@ -4516,12 +4515,12 @@ PORTVERSION= 1.0</programlisting>
<title>Installing a whole tree of files</title>
<para>Sometimes, there is a need to install a big number of
files, preserving their hierarchical organization, ie.
files, preserving their hierarchical organization, i.e.,
copying over a whole directory tree from
<makevar>WRKSRC</makevar> to a target directory under
<makevar>PREFIX</makevar>.</para>
<para>Two macros exists for this situation. The advantage of
<para>Two macros exist for this situation. The advantage of
using these macros instead of <command>cp</command> is that
they guarantee proper file ownership and permissions on
target files. The first macro,
@ -5309,7 +5308,7 @@ IGNORE= may not be redistributed because of licensing reasons. Please visit <rep
have optional argument variables,
<makevar>AUTOMAKE_ARGS</makevar> and
<makevar>ACLOCAL_ARGS</makevar> respectively, which may be
overriden by the port <filename>Makefile</filename> if
overridden by the port <filename>Makefile</filename> if
required.</para>
</sect2>
</sect1>
@ -5840,9 +5839,9 @@ USE_XORG= x11 xpm</programlisting>
<para>The list of possible categories is available on the
<ulink
url="http://standards.freedesktop.org/menu-spec/latest/apa.html">Freedesktop
website</ulink>. The <makevar>StartupNotify</makevar>
indicates, if the application will clear the status in
startup notification aware environment.</para>
website</ulink>. <makevar>StartupNotify</makevar>
indicates whether the application will clear the status in
a startup notification-aware environment.</para>
<para>Example:</para>
@ -6787,13 +6786,13 @@ QT_COMPONENTS= qmake_build moc_build rcc_build uic_build</programlisting>
<row>
<entry><makevar>APXS</makevar></entry>
<entry>Full path to the <command>apxs</command>
binary. Can be overriden in your port.</entry>
binary. Can be overridden in your port.</entry>
</row>
<row>
<entry><makevar>HTTPD</makevar></entry>
<entry>Full path to the <command>httpd</command>
binary. Can be overriden in your port.</entry>
binary. Can be overridden in your port.</entry>
</row>
<row>
@ -6846,7 +6845,7 @@ QT_COMPONENTS= qmake_build moc_build rcc_build uic_build</programlisting>
<entry><makevar>SHORTMODNAME</makevar></entry>
<entry>Short name of the module. Automatically
derived from <makevar>MODULENAME</makevar>, but can
be overriden. Example:
be overridden. Example:
<literal>hello</literal></entry>
</row>
@ -8259,8 +8258,8 @@ PLIST_SUB+= VERSION="${VER_STR}"
<para>The following fragment is from a port which can use
<application>Lua</application> version
<literal>5.0</literal> or <literal>5.1</literal>, and uses
<literal>5.0</literal> by default. It can be overriden by
the user using <makevar>WITH_LUA_VER</makevar>.</para>
<literal>5.0</literal> by default. It can be overridden
by the user with <makevar>WITH_LUA_VER</makevar>.</para>
<programlisting>USE_LUA= 5.0-5.1
WANT_LUA_VER= 5.0</programlisting>
@ -14207,7 +14206,7 @@ Reference: &lt;http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
<entry>March 18, 2009</entry>
<entry>8.0-CURRENT after the dynamic string token
substitution has been implemented for rpath and needed
pathes.</entry>
paths.</entry>
</row>
<row>