os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Lots of minor changes and a few typo/grammar fixes including:

Browse source 
:- -> :
licence -> license
bsd.ports{.*.mk} -> bsd.port{.*.mk}
use consistent smileys.. :) -> :-) and :> to :->
This commit is contained in:
Jim Mock 1999-11-17 22:34:23 +00:00
parent 465e059a52
commit a80e769e50
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=6079
4 changed files with 168 additions and 164 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

83
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.59 1999/10/07 16:33:03 marcel Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.60 1999/11/15 02:36:17 obrien Exp $
-->
<chapter id="ports">
@ -40,7 +40,7 @@
<para>The base FreeBSD system comes with a very wide range of tools and
system utilities, but a lot of popular programs are not in the base
system, for good reasons:-</para>
system, for good reasons:</para>
<orderedlist>
<listitem>
@ -147,7 +147,7 @@ install -c -o root -g wheel -m 444 /usr/ports/devel/ElectricFence/work/ElectricF
output.</para>
<para>If you tried this yourself, you may well have got something like
this at the start:-</para>
this at the start:</para>
<screen id="ports-fetch">&prompt.root; <userinput>make install</userinput>
&gt;&gt; ElectricFence-2.0.5.tar.gz doesn't seem to exist on this system.
@ -281,7 +281,7 @@ WRKDIRPREFIX= /tmp</programlisting>
on-the-fly <link linkend="ports-tarball">tarballs</link> for you.
Here is how it works, with the gnats program in the databases
directory as an example (the bits in square brackets are comments. Do
not type them in if you are trying this yourself!):-</para>
not type them in if you are trying this yourself!):</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>mkdir databases</userinput>
@ -314,7 +314,7 @@ password. Remember to use binary (also known as image) mode!]
<para>Let us try something more ambitious now. Instead of getting a
single port skeleton, we will get a whole sub-directory, for example all
the database skeletons in the ports collection. It looks almost the
same:-</para>
same:</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>ftp ftp.FreeBSD.org</userinput>
@ -355,7 +355,7 @@ password. Remember to use binary (also known as image) mode!]
<para>The most important component of a skeleton is the Makefile. This
contains various statements that specify how the port should be
compiled and installed. Here is the Makefile for
ElectricFence:-</para>
ElectricFence:</para>
<programlisting>
# New ports collection makefile for: Electric Fence
@ -446,7 +446,7 @@ do-install:
<sect2>
<title>The <filename>pkg</filename> directory</title>
<para>This program contains three quite useful files:-</para>
<para>This program contains three quite useful files:</para>
<itemizedlist>
<listitem>
@ -548,7 +548,7 @@ do-install:
</question>
<answer>
<para>Several reasons:-</para>
<para>Several reasons:</para>
<orderedlist>
<listitem>
@ -578,7 +578,7 @@ do-install:
<listitem>
<para>Some people like having code around, so they can read it if
they get bored, hack around with it, borrow from it (licence
they get bored, hack around with it, borrow from it (license
terms permitting, of course!) and so on.</para>
</listitem>
@ -626,7 +626,7 @@ do-install:
<para>You can see what files are in them, or even extract them
yourself, by using the standard Unix tar program, which comes with
the base FreeBSD system, like this:-</para>
the base FreeBSD system, like this:</para>
<screen>&prompt.user; <userinput>tar tvzf foobar.tar.gz</userinput>
&prompt.user; <userinput>tar xzvf foobar.tar.gz</userinput>
@ -689,7 +689,7 @@ do-install:
<filename>/usr/ports/distfiles</filename>, but you will not be able
to copy anything there because it is sym-linked to the CDROM, which
is read-only. You can tell it to look somewhere else by
doing</para>
doing:</para>
<screen>&prompt.root; <userinput>make DISTDIR=<replaceable>/where/you/put/it</replaceable> install</userinput></screen>
</answer>
@ -769,8 +769,7 @@ do-install:
<answer>
<para>Yes. If you know, for example, <hostid
role="fqdn">ftp.FreeBSD.org</hostid> is much closer than sites
listed in <makevar>MASTER_SITES</makevar>, do as following
example.</para>
listed in <makevar>MASTER_SITES</makevar>, do as follows:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
@ -888,11 +887,11 @@ do-install:
</question>
<answer>
<para>No problem, just do</para>
<para>No problem, just do:</para>
<screen>&prompt.root; <userinput>pkg_delete grizzle-6.5</userinput></screen>
<para>Alternatively, you can do</para>
<para>Alternatively, you can do:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/grizzle</replaceable></userinput>
&prompt.root; <userinput>make deinstall</userinput></screen>
@ -945,7 +944,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Yes, if you are sure you have finished with them, those can
go as well.</para>
go as well. They can be removed manually, or by using
<command>make distclean</command>.</para>
</answer>
</qandaentry>
@ -987,7 +987,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>OK, do this before you go to bed/work/the local
park:-</para>
park:</para>
<screen>&prompt.root <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>make -DBATCH install</userinput></screen>
@ -1012,7 +1012,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>No problem, assuming you know how to make patches for your
changes:-</para>
changes:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/frobble</replaceable></userinput>
&prompt.root; <userinput>make extract</userinput>
@ -1031,8 +1031,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Nothing secret about it at all, just look at the
<filename>bsd.ports.mk</filename> and
<filename>bsd.ports.subdir.mk</filename> files in your <ulink
<filename>bsd.port.mk</filename> and
<filename>bsd.port.subdir.mk</filename> files in your <ulink
url="file://localhost/usr/ports/Mk/">makefiles
directory.</ulink></para>
@ -1063,14 +1063,15 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
Additionally, you may send specific questions to &a.ports;.</para>
<note>
<para>Only a fraction of the overridable variables
(<makevar><replaceable>VAR</replaceable></makevar>) are mentioned in
this document. Most (if not all) are documented at the start of
<filename>bsd.port.mk</filename>. This file users a non-standard tab
setting. <application>Emacs</application> and
<application>Vim</application> should recognise the setting on loading
the file. Both <command>vi</command> and <command>ex</command> can be
set to use the correct value by typing <command>:set tabstop=4</command>
<para>Only a fraction of the variables
(<makevar><replaceable>VAR</replaceable></makevar>) that can be
overridden are mentioned in this document. Most (if not all) are
documented at the start of <filename>bsd.port.mk</filename>. This
file uses a non-standard tab setting.
<application>Emacs</application> and <application>Vim</application>
should recognise the setting on loading the file. Both
<command>vi</command> and <command>ex</command> can be set to use
the correct value by typing <command>:set tabstop=4</command>
once the file has been loaded.</para>
</note>
@ -1355,7 +1356,7 @@ lib/X11/oneko/mouse.xpm
it in the tree. Your name will also appear in the list of
&ldquo;Additional FreeBSD contributors&rdquo; on the FreeBSD
Handbook and other files. Isn't that great?!? <!-- smiley
-->:)</para>
-->:-)</para>
</sect3>
</sect2>
@ -1377,7 +1378,7 @@ lib/X11/oneko/mouse.xpm
<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>
<!-- smiley --><emphasis>:-&gt;</emphasis></para>
<procedure>
@ -1517,7 +1518,7 @@ lib/X11/oneko/mouse.xpm
by putting it on
<filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename>
as the last resort. Please refer to this location as
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports;if
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports; if
you are not sure what to do.</para>
<para>If your port's distfile changes all the time for no good reason,
@ -1705,7 +1706,7 @@ lib/X11/oneko/mouse.xpm
linkend="porting-categories">categories</link> section for more
discussion about how to pick the right categories.</para>
<para>If you port truly belongs to something that is different from
<para>If your port truly belongs to something that is different from
all the existing ones, you can even create a new category name. In
that case, please send mail to the &a.ports; to propose a new
category.</para>
@ -1802,7 +1803,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<title><makevar>MAINTAINER</makevar></title>
<para>Set your mail-address here. Please. <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
<para>For detailed description of the responsibility of maintainers,
refer to <link linkend="policies-maintainer">MAINTAINER on
@ -2042,7 +2043,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<maketarget>install.man</maketarget> target,
<literal>NO_INSTALL_MANPAGES=yes</literal> should be set. In
addition, the author of the original port should be shot. <!--
smiley --><emphasis>:&gt;</emphasis></para>
smiley --><emphasis>:-&gt;</emphasis></para>
<para>If your port's source <filename>Makefile</filename> has
something else than <maketarget>all</maketarget> as the main build
@ -2111,7 +2112,7 @@ lib/libtvl80.so.1
<sect3>
<title>Moving a.out libraries out of the way</title>
<para>A.out libraries should be moved out of
<para>Any a.out libraries should be moved out of
<filename>/usr/local/lib</filename> and similar to an
<filename>aout</filename> subdirectory. (If you do not move them out
of the way, ELF ports will happily overwrite a.out libraries.) The
@ -2298,7 +2299,7 @@ RESOLUTION?= 300
build the port normally.</para>
<para>As for other resolutions, this is the <emphasis>entire</emphasis>
<filename>xdvi118/Makefile</filename>;</para>
<filename>xdvi118/Makefile</filename>:</para>
<programlisting>
RESOLUTION= 118
@ -2758,7 +2759,7 @@ diff -u -r1.15 PLIST
<step>
<para><link linkend="porting-testing">Test</link> and admire your
work. <!-- smiley --><emphasis>:)</emphasis>. Check the
work. <!-- smiley --><emphasis>:-)</emphasis>. Check the
<filename>dir</filename> file before and after each step.</para>
</step>
</procedure>
@ -3253,7 +3254,7 @@ post-install:
</row>
<row>
<entry>2.1-CURRENTs</entry>
<entry>2.1-CURRENT</entry>
<entry>199501, 199503</entry>
</row>
@ -3558,7 +3559,7 @@ post-install:
<filename>bsd.port.mk</filename></title>
<para>Do not write anything after the <literal>.include
&lt;bsd.port.mk&gt;</literal> line. it usually can be avoided by
&lt;bsd.port.mk&gt;</literal> line. It usually can be avoided by
including <filename>bsd.port.pre.mk</filename> somewhere in the
middle of your <filename>Makefile</filename> and
<filename>bsd.port.post.mk</filename> at the end.</para>
@ -4023,7 +4024,7 @@ mysql:*:88:88:MySQL Daemon:/var/db/mysql:/sbin/nologin</programlisting>
<para>Do ask us questions if you have any trouble! Do not just beat
your head against a wall! <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
</sect3>
</sect2>
@ -4789,7 +4790,7 @@ pre-install:
following us to here, really. Now that you know how to do a port,
have at it and convert everything in the world into ports! That
is the easiest way to start contributing to the FreeBSD Project!
<!-- smiley --><emphasis>:)</emphasis></para>
<!-- smiley --><emphasis>:-)</emphasis></para>
</sect2>
</sect1>
</chapter>

83
en_US.ISO8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.59 1999/10/07 16:33:03 marcel Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.60 1999/11/15 02:36:17 obrien Exp $
-->
<chapter id="ports">
@ -40,7 +40,7 @@
<para>The base FreeBSD system comes with a very wide range of tools and
system utilities, but a lot of popular programs are not in the base
system, for good reasons:-</para>
system, for good reasons:</para>
<orderedlist>
<listitem>
@ -147,7 +147,7 @@ install -c -o root -g wheel -m 444 /usr/ports/devel/ElectricFence/work/ElectricF
output.</para>
<para>If you tried this yourself, you may well have got something like
this at the start:-</para>
this at the start:</para>
<screen id="ports-fetch">&prompt.root; <userinput>make install</userinput>
&gt;&gt; ElectricFence-2.0.5.tar.gz doesn't seem to exist on this system.
@ -281,7 +281,7 @@ WRKDIRPREFIX= /tmp</programlisting>
on-the-fly <link linkend="ports-tarball">tarballs</link> for you.
Here is how it works, with the gnats program in the databases
directory as an example (the bits in square brackets are comments. Do
not type them in if you are trying this yourself!):-</para>
not type them in if you are trying this yourself!):</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>mkdir databases</userinput>
@ -314,7 +314,7 @@ password. Remember to use binary (also known as image) mode!]
<para>Let us try something more ambitious now. Instead of getting a
single port skeleton, we will get a whole sub-directory, for example all
the database skeletons in the ports collection. It looks almost the
same:-</para>
same:</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>ftp ftp.FreeBSD.org</userinput>
@ -355,7 +355,7 @@ password. Remember to use binary (also known as image) mode!]
<para>The most important component of a skeleton is the Makefile. This
contains various statements that specify how the port should be
compiled and installed. Here is the Makefile for
ElectricFence:-</para>
ElectricFence:</para>
<programlisting>
# New ports collection makefile for: Electric Fence
@ -446,7 +446,7 @@ do-install:
<sect2>
<title>The <filename>pkg</filename> directory</title>
<para>This program contains three quite useful files:-</para>
<para>This program contains three quite useful files:</para>
<itemizedlist>
<listitem>
@ -548,7 +548,7 @@ do-install:
</question>
<answer>
<para>Several reasons:-</para>
<para>Several reasons:</para>
<orderedlist>
<listitem>
@ -578,7 +578,7 @@ do-install:
<listitem>
<para>Some people like having code around, so they can read it if
they get bored, hack around with it, borrow from it (licence
they get bored, hack around with it, borrow from it (license
terms permitting, of course!) and so on.</para>
</listitem>
@ -626,7 +626,7 @@ do-install:
<para>You can see what files are in them, or even extract them
yourself, by using the standard Unix tar program, which comes with
the base FreeBSD system, like this:-</para>
the base FreeBSD system, like this:</para>
<screen>&prompt.user; <userinput>tar tvzf foobar.tar.gz</userinput>
&prompt.user; <userinput>tar xzvf foobar.tar.gz</userinput>
@ -689,7 +689,7 @@ do-install:
<filename>/usr/ports/distfiles</filename>, but you will not be able
to copy anything there because it is sym-linked to the CDROM, which
is read-only. You can tell it to look somewhere else by
doing</para>
doing:</para>
<screen>&prompt.root; <userinput>make DISTDIR=<replaceable>/where/you/put/it</replaceable> install</userinput></screen>
</answer>
@ -769,8 +769,7 @@ do-install:
<answer>
<para>Yes. If you know, for example, <hostid
role="fqdn">ftp.FreeBSD.org</hostid> is much closer than sites
listed in <makevar>MASTER_SITES</makevar>, do as following
example.</para>
listed in <makevar>MASTER_SITES</makevar>, do as follows:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
@ -888,11 +887,11 @@ do-install:
</question>
<answer>
<para>No problem, just do</para>
<para>No problem, just do:</para>
<screen>&prompt.root; <userinput>pkg_delete grizzle-6.5</userinput></screen>
<para>Alternatively, you can do</para>
<para>Alternatively, you can do:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/grizzle</replaceable></userinput>
&prompt.root; <userinput>make deinstall</userinput></screen>
@ -945,7 +944,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Yes, if you are sure you have finished with them, those can
go as well.</para>
go as well. They can be removed manually, or by using
<command>make distclean</command>.</para>
</answer>
</qandaentry>
@ -987,7 +987,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>OK, do this before you go to bed/work/the local
park:-</para>
park:</para>
<screen>&prompt.root <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>make -DBATCH install</userinput></screen>
@ -1012,7 +1012,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>No problem, assuming you know how to make patches for your
changes:-</para>
changes:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/frobble</replaceable></userinput>
&prompt.root; <userinput>make extract</userinput>
@ -1031,8 +1031,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Nothing secret about it at all, just look at the
<filename>bsd.ports.mk</filename> and
<filename>bsd.ports.subdir.mk</filename> files in your <ulink
<filename>bsd.port.mk</filename> and
<filename>bsd.port.subdir.mk</filename> files in your <ulink
url="file://localhost/usr/ports/Mk/">makefiles
directory.</ulink></para>
@ -1063,14 +1063,15 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
Additionally, you may send specific questions to &a.ports;.</para>
<note>
<para>Only a fraction of the overridable variables
(<makevar><replaceable>VAR</replaceable></makevar>) are mentioned in
this document. Most (if not all) are documented at the start of
<filename>bsd.port.mk</filename>. This file users a non-standard tab
setting. <application>Emacs</application> and
<application>Vim</application> should recognise the setting on loading
the file. Both <command>vi</command> and <command>ex</command> can be
set to use the correct value by typing <command>:set tabstop=4</command>
<para>Only a fraction of the variables
(<makevar><replaceable>VAR</replaceable></makevar>) that can be
overridden are mentioned in this document. Most (if not all) are
documented at the start of <filename>bsd.port.mk</filename>. This
file uses a non-standard tab setting.
<application>Emacs</application> and <application>Vim</application>
should recognise the setting on loading the file. Both
<command>vi</command> and <command>ex</command> can be set to use
the correct value by typing <command>:set tabstop=4</command>
once the file has been loaded.</para>
</note>
@ -1355,7 +1356,7 @@ lib/X11/oneko/mouse.xpm
it in the tree. Your name will also appear in the list of
&ldquo;Additional FreeBSD contributors&rdquo; on the FreeBSD
Handbook and other files. Isn't that great?!? <!-- smiley
-->:)</para>
-->:-)</para>
</sect3>
</sect2>
@ -1377,7 +1378,7 @@ lib/X11/oneko/mouse.xpm
<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>
<!-- smiley --><emphasis>:-&gt;</emphasis></para>
<procedure>
@ -1517,7 +1518,7 @@ lib/X11/oneko/mouse.xpm
by putting it on
<filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename>
as the last resort. Please refer to this location as
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports;if
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports; if
you are not sure what to do.</para>
<para>If your port's distfile changes all the time for no good reason,
@ -1705,7 +1706,7 @@ lib/X11/oneko/mouse.xpm
linkend="porting-categories">categories</link> section for more
discussion about how to pick the right categories.</para>
<para>If you port truly belongs to something that is different from
<para>If your port truly belongs to something that is different from
all the existing ones, you can even create a new category name. In
that case, please send mail to the &a.ports; to propose a new
category.</para>
@ -1802,7 +1803,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<title><makevar>MAINTAINER</makevar></title>
<para>Set your mail-address here. Please. <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
<para>For detailed description of the responsibility of maintainers,
refer to <link linkend="policies-maintainer">MAINTAINER on
@ -2042,7 +2043,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<maketarget>install.man</maketarget> target,
<literal>NO_INSTALL_MANPAGES=yes</literal> should be set. In
addition, the author of the original port should be shot. <!--
smiley --><emphasis>:&gt;</emphasis></para>
smiley --><emphasis>:-&gt;</emphasis></para>
<para>If your port's source <filename>Makefile</filename> has
something else than <maketarget>all</maketarget> as the main build
@ -2111,7 +2112,7 @@ lib/libtvl80.so.1
<sect3>
<title>Moving a.out libraries out of the way</title>
<para>A.out libraries should be moved out of
<para>Any a.out libraries should be moved out of
<filename>/usr/local/lib</filename> and similar to an
<filename>aout</filename> subdirectory. (If you do not move them out
of the way, ELF ports will happily overwrite a.out libraries.) The
@ -2298,7 +2299,7 @@ RESOLUTION?= 300
build the port normally.</para>
<para>As for other resolutions, this is the <emphasis>entire</emphasis>
<filename>xdvi118/Makefile</filename>;</para>
<filename>xdvi118/Makefile</filename>:</para>
<programlisting>
RESOLUTION= 118
@ -2758,7 +2759,7 @@ diff -u -r1.15 PLIST
<step>
<para><link linkend="porting-testing">Test</link> and admire your
work. <!-- smiley --><emphasis>:)</emphasis>. Check the
work. <!-- smiley --><emphasis>:-)</emphasis>. Check the
<filename>dir</filename> file before and after each step.</para>
</step>
</procedure>
@ -3253,7 +3254,7 @@ post-install:
</row>
<row>
<entry>2.1-CURRENTs</entry>
<entry>2.1-CURRENT</entry>
<entry>199501, 199503</entry>
</row>
@ -3558,7 +3559,7 @@ post-install:
<filename>bsd.port.mk</filename></title>
<para>Do not write anything after the <literal>.include
&lt;bsd.port.mk&gt;</literal> line. it usually can be avoided by
&lt;bsd.port.mk&gt;</literal> line. It usually can be avoided by
including <filename>bsd.port.pre.mk</filename> somewhere in the
middle of your <filename>Makefile</filename> and
<filename>bsd.port.post.mk</filename> at the end.</para>
@ -4023,7 +4024,7 @@ mysql:*:88:88:MySQL Daemon:/var/db/mysql:/sbin/nologin</programlisting>
<para>Do ask us questions if you have any trouble! Do not just beat
your head against a wall! <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
</sect3>
</sect2>
@ -4789,7 +4790,7 @@ pre-install:
following us to here, really. Now that you know how to do a port,
have at it and convert everything in the world into ports! That
is the easiest way to start contributing to the FreeBSD Project!
<!-- smiley --><emphasis>:)</emphasis></para>
<!-- smiley --><emphasis>:-)</emphasis></para>
</sect2>
</sect1>
</chapter>

83
en_US.ISO_8859-1/books/handbook/ports/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.59 1999/10/07 16:33:03 marcel Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.60 1999/11/15 02:36:17 obrien Exp $
-->
<chapter id="ports">
@ -40,7 +40,7 @@
<para>The base FreeBSD system comes with a very wide range of tools and
system utilities, but a lot of popular programs are not in the base
system, for good reasons:-</para>
system, for good reasons:</para>
<orderedlist>
<listitem>
@ -147,7 +147,7 @@ install -c -o root -g wheel -m 444 /usr/ports/devel/ElectricFence/work/ElectricF
output.</para>
<para>If you tried this yourself, you may well have got something like
this at the start:-</para>
this at the start:</para>
<screen id="ports-fetch">&prompt.root; <userinput>make install</userinput>
&gt;&gt; ElectricFence-2.0.5.tar.gz doesn't seem to exist on this system.
@ -281,7 +281,7 @@ WRKDIRPREFIX= /tmp</programlisting>
on-the-fly <link linkend="ports-tarball">tarballs</link> for you.
Here is how it works, with the gnats program in the databases
directory as an example (the bits in square brackets are comments. Do
not type them in if you are trying this yourself!):-</para>
not type them in if you are trying this yourself!):</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>mkdir databases</userinput>
@ -314,7 +314,7 @@ password. Remember to use binary (also known as image) mode!]
<para>Let us try something more ambitious now. Instead of getting a
single port skeleton, we will get a whole sub-directory, for example all
the database skeletons in the ports collection. It looks almost the
same:-</para>
same:</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>ftp ftp.FreeBSD.org</userinput>
@ -355,7 +355,7 @@ password. Remember to use binary (also known as image) mode!]
<para>The most important component of a skeleton is the Makefile. This
contains various statements that specify how the port should be
compiled and installed. Here is the Makefile for
ElectricFence:-</para>
ElectricFence:</para>
<programlisting>
# New ports collection makefile for: Electric Fence
@ -446,7 +446,7 @@ do-install:
<sect2>
<title>The <filename>pkg</filename> directory</title>
<para>This program contains three quite useful files:-</para>
<para>This program contains three quite useful files:</para>
<itemizedlist>
<listitem>
@ -548,7 +548,7 @@ do-install:
</question>
<answer>
<para>Several reasons:-</para>
<para>Several reasons:</para>
<orderedlist>
<listitem>
@ -578,7 +578,7 @@ do-install:
<listitem>
<para>Some people like having code around, so they can read it if
they get bored, hack around with it, borrow from it (licence
they get bored, hack around with it, borrow from it (license
terms permitting, of course!) and so on.</para>
</listitem>
@ -626,7 +626,7 @@ do-install:
<para>You can see what files are in them, or even extract them
yourself, by using the standard Unix tar program, which comes with
the base FreeBSD system, like this:-</para>
the base FreeBSD system, like this:</para>
<screen>&prompt.user; <userinput>tar tvzf foobar.tar.gz</userinput>
&prompt.user; <userinput>tar xzvf foobar.tar.gz</userinput>
@ -689,7 +689,7 @@ do-install:
<filename>/usr/ports/distfiles</filename>, but you will not be able
to copy anything there because it is sym-linked to the CDROM, which
is read-only. You can tell it to look somewhere else by
doing</para>
doing:</para>
<screen>&prompt.root; <userinput>make DISTDIR=<replaceable>/where/you/put/it</replaceable> install</userinput></screen>
</answer>
@ -769,8 +769,7 @@ do-install:
<answer>
<para>Yes. If you know, for example, <hostid
role="fqdn">ftp.FreeBSD.org</hostid> is much closer than sites
listed in <makevar>MASTER_SITES</makevar>, do as following
example.</para>
listed in <makevar>MASTER_SITES</makevar>, do as follows:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
@ -888,11 +887,11 @@ do-install:
</question>
<answer>
<para>No problem, just do</para>
<para>No problem, just do:</para>
<screen>&prompt.root; <userinput>pkg_delete grizzle-6.5</userinput></screen>
<para>Alternatively, you can do</para>
<para>Alternatively, you can do:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/grizzle</replaceable></userinput>
&prompt.root; <userinput>make deinstall</userinput></screen>
@ -945,7 +944,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Yes, if you are sure you have finished with them, those can
go as well.</para>
go as well. They can be removed manually, or by using
<command>make distclean</command>.</para>
</answer>
</qandaentry>
@ -987,7 +987,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>OK, do this before you go to bed/work/the local
park:-</para>
park:</para>
<screen>&prompt.root <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>make -DBATCH install</userinput></screen>
@ -1012,7 +1012,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>No problem, assuming you know how to make patches for your
changes:-</para>
changes:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/frobble</replaceable></userinput>
&prompt.root; <userinput>make extract</userinput>
@ -1031,8 +1031,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Nothing secret about it at all, just look at the
<filename>bsd.ports.mk</filename> and
<filename>bsd.ports.subdir.mk</filename> files in your <ulink
<filename>bsd.port.mk</filename> and
<filename>bsd.port.subdir.mk</filename> files in your <ulink
url="file://localhost/usr/ports/Mk/">makefiles
directory.</ulink></para>
@ -1063,14 +1063,15 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
Additionally, you may send specific questions to &a.ports;.</para>
<note>
<para>Only a fraction of the overridable variables
(<makevar><replaceable>VAR</replaceable></makevar>) are mentioned in
this document. Most (if not all) are documented at the start of
<filename>bsd.port.mk</filename>. This file users a non-standard tab
setting. <application>Emacs</application> and
<application>Vim</application> should recognise the setting on loading
the file. Both <command>vi</command> and <command>ex</command> can be
set to use the correct value by typing <command>:set tabstop=4</command>
<para>Only a fraction of the variables
(<makevar><replaceable>VAR</replaceable></makevar>) that can be
overridden are mentioned in this document. Most (if not all) are
documented at the start of <filename>bsd.port.mk</filename>. This
file uses a non-standard tab setting.
<application>Emacs</application> and <application>Vim</application>
should recognise the setting on loading the file. Both
<command>vi</command> and <command>ex</command> can be set to use
the correct value by typing <command>:set tabstop=4</command>
once the file has been loaded.</para>
</note>
@ -1355,7 +1356,7 @@ lib/X11/oneko/mouse.xpm
it in the tree. Your name will also appear in the list of
&ldquo;Additional FreeBSD contributors&rdquo; on the FreeBSD
Handbook and other files. Isn't that great?!? <!-- smiley
-->:)</para>
-->:-)</para>
</sect3>
</sect2>
@ -1377,7 +1378,7 @@ lib/X11/oneko/mouse.xpm
<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>
<!-- smiley --><emphasis>:-&gt;</emphasis></para>
<procedure>
@ -1517,7 +1518,7 @@ lib/X11/oneko/mouse.xpm
by putting it on
<filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename>
as the last resort. Please refer to this location as
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports;if
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports; if
you are not sure what to do.</para>
<para>If your port's distfile changes all the time for no good reason,
@ -1705,7 +1706,7 @@ lib/X11/oneko/mouse.xpm
linkend="porting-categories">categories</link> section for more
discussion about how to pick the right categories.</para>
<para>If you port truly belongs to something that is different from
<para>If your port truly belongs to something that is different from
all the existing ones, you can even create a new category name. In
that case, please send mail to the &a.ports; to propose a new
category.</para>
@ -1802,7 +1803,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<title><makevar>MAINTAINER</makevar></title>
<para>Set your mail-address here. Please. <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
<para>For detailed description of the responsibility of maintainers,
refer to <link linkend="policies-maintainer">MAINTAINER on
@ -2042,7 +2043,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<maketarget>install.man</maketarget> target,
<literal>NO_INSTALL_MANPAGES=yes</literal> should be set. In
addition, the author of the original port should be shot. <!--
smiley --><emphasis>:&gt;</emphasis></para>
smiley --><emphasis>:-&gt;</emphasis></para>
<para>If your port's source <filename>Makefile</filename> has
something else than <maketarget>all</maketarget> as the main build
@ -2111,7 +2112,7 @@ lib/libtvl80.so.1
<sect3>
<title>Moving a.out libraries out of the way</title>
<para>A.out libraries should be moved out of
<para>Any a.out libraries should be moved out of
<filename>/usr/local/lib</filename> and similar to an
<filename>aout</filename> subdirectory. (If you do not move them out
of the way, ELF ports will happily overwrite a.out libraries.) The
@ -2298,7 +2299,7 @@ RESOLUTION?= 300
build the port normally.</para>
<para>As for other resolutions, this is the <emphasis>entire</emphasis>
<filename>xdvi118/Makefile</filename>;</para>
<filename>xdvi118/Makefile</filename>:</para>
<programlisting>
RESOLUTION= 118
@ -2758,7 +2759,7 @@ diff -u -r1.15 PLIST
<step>
<para><link linkend="porting-testing">Test</link> and admire your
work. <!-- smiley --><emphasis>:)</emphasis>. Check the
work. <!-- smiley --><emphasis>:-)</emphasis>. Check the
<filename>dir</filename> file before and after each step.</para>
</step>
</procedure>
@ -3253,7 +3254,7 @@ post-install:
</row>
<row>
<entry>2.1-CURRENTs</entry>
<entry>2.1-CURRENT</entry>
<entry>199501, 199503</entry>
</row>
@ -3558,7 +3559,7 @@ post-install:
<filename>bsd.port.mk</filename></title>
<para>Do not write anything after the <literal>.include
&lt;bsd.port.mk&gt;</literal> line. it usually can be avoided by
&lt;bsd.port.mk&gt;</literal> line. It usually can be avoided by
including <filename>bsd.port.pre.mk</filename> somewhere in the
middle of your <filename>Makefile</filename> and
<filename>bsd.port.post.mk</filename> at the end.</para>
@ -4023,7 +4024,7 @@ mysql:*:88:88:MySQL Daemon:/var/db/mysql:/sbin/nologin</programlisting>
<para>Do ask us questions if you have any trouble! Do not just beat
your head against a wall! <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
</sect3>
</sect2>
@ -4789,7 +4790,7 @@ pre-install:
following us to here, really. Now that you know how to do a port,
have at it and convert everything in the world into ports! That
is the easiest way to start contributing to the FreeBSD Project!
<!-- smiley --><emphasis>:)</emphasis></para>
<!-- smiley --><emphasis>:-)</emphasis></para>
</sect2>
</sect1>
</chapter>

83
en_US.ISO_8859-1/books/porters-handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.59 1999/10/07 16:33:03 marcel Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.60 1999/11/15 02:36:17 obrien Exp $
-->
<chapter id="ports">
@ -40,7 +40,7 @@
<para>The base FreeBSD system comes with a very wide range of tools and
system utilities, but a lot of popular programs are not in the base
system, for good reasons:-</para>
system, for good reasons:</para>
<orderedlist>
<listitem>
@ -147,7 +147,7 @@ install -c -o root -g wheel -m 444 /usr/ports/devel/ElectricFence/work/ElectricF
output.</para>
<para>If you tried this yourself, you may well have got something like
this at the start:-</para>
this at the start:</para>
<screen id="ports-fetch">&prompt.root; <userinput>make install</userinput>
&gt;&gt; ElectricFence-2.0.5.tar.gz doesn't seem to exist on this system.
@ -281,7 +281,7 @@ WRKDIRPREFIX= /tmp</programlisting>
on-the-fly <link linkend="ports-tarball">tarballs</link> for you.
Here is how it works, with the gnats program in the databases
directory as an example (the bits in square brackets are comments. Do
not type them in if you are trying this yourself!):-</para>
not type them in if you are trying this yourself!):</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>mkdir databases</userinput>
@ -314,7 +314,7 @@ password. Remember to use binary (also known as image) mode!]
<para>Let us try something more ambitious now. Instead of getting a
single port skeleton, we will get a whole sub-directory, for example all
the database skeletons in the ports collection. It looks almost the
same:-</para>
same:</para>
<screen>&prompt.root; <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>ftp ftp.FreeBSD.org</userinput>
@ -355,7 +355,7 @@ password. Remember to use binary (also known as image) mode!]
<para>The most important component of a skeleton is the Makefile. This
contains various statements that specify how the port should be
compiled and installed. Here is the Makefile for
ElectricFence:-</para>
ElectricFence:</para>
<programlisting>
# New ports collection makefile for: Electric Fence
@ -446,7 +446,7 @@ do-install:
<sect2>
<title>The <filename>pkg</filename> directory</title>
<para>This program contains three quite useful files:-</para>
<para>This program contains three quite useful files:</para>
<itemizedlist>
<listitem>
@ -548,7 +548,7 @@ do-install:
</question>
<answer>
<para>Several reasons:-</para>
<para>Several reasons:</para>
<orderedlist>
<listitem>
@ -578,7 +578,7 @@ do-install:
<listitem>
<para>Some people like having code around, so they can read it if
they get bored, hack around with it, borrow from it (licence
they get bored, hack around with it, borrow from it (license
terms permitting, of course!) and so on.</para>
</listitem>
@ -626,7 +626,7 @@ do-install:
<para>You can see what files are in them, or even extract them
yourself, by using the standard Unix tar program, which comes with
the base FreeBSD system, like this:-</para>
the base FreeBSD system, like this:</para>
<screen>&prompt.user; <userinput>tar tvzf foobar.tar.gz</userinput>
&prompt.user; <userinput>tar xzvf foobar.tar.gz</userinput>
@ -689,7 +689,7 @@ do-install:
<filename>/usr/ports/distfiles</filename>, but you will not be able
to copy anything there because it is sym-linked to the CDROM, which
is read-only. You can tell it to look somewhere else by
doing</para>
doing:</para>
<screen>&prompt.root; <userinput>make DISTDIR=<replaceable>/where/you/put/it</replaceable> install</userinput></screen>
</answer>
@ -769,8 +769,7 @@ do-install:
<answer>
<para>Yes. If you know, for example, <hostid
role="fqdn">ftp.FreeBSD.org</hostid> is much closer than sites
listed in <makevar>MASTER_SITES</makevar>, do as following
example.</para>
listed in <makevar>MASTER_SITES</makevar>, do as follows:</para>
<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE=ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
@ -888,11 +887,11 @@ do-install:
</question>
<answer>
<para>No problem, just do</para>
<para>No problem, just do:</para>
<screen>&prompt.root; <userinput>pkg_delete grizzle-6.5</userinput></screen>
<para>Alternatively, you can do</para>
<para>Alternatively, you can do:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/grizzle</replaceable></userinput>
&prompt.root; <userinput>make deinstall</userinput></screen>
@ -945,7 +944,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Yes, if you are sure you have finished with them, those can
go as well.</para>
go as well. They can be removed manually, or by using
<command>make distclean</command>.</para>
</answer>
</qandaentry>
@ -987,7 +987,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>OK, do this before you go to bed/work/the local
park:-</para>
park:</para>
<screen>&prompt.root <userinput>cd /usr/ports</userinput>
&prompt.root; <userinput>make -DBATCH install</userinput></screen>
@ -1012,7 +1012,7 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>No problem, assuming you know how to make patches for your
changes:-</para>
changes:</para>
<screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/frobble</replaceable></userinput>
&prompt.root; <userinput>make extract</userinput>
@ -1031,8 +1031,8 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
<answer>
<para>Nothing secret about it at all, just look at the
<filename>bsd.ports.mk</filename> and
<filename>bsd.ports.subdir.mk</filename> files in your <ulink
<filename>bsd.port.mk</filename> and
<filename>bsd.port.subdir.mk</filename> files in your <ulink
url="file://localhost/usr/ports/Mk/">makefiles
directory.</ulink></para>
@ -1063,14 +1063,15 @@ grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up arc
Additionally, you may send specific questions to &a.ports;.</para>
<note>
<para>Only a fraction of the overridable variables
(<makevar><replaceable>VAR</replaceable></makevar>) are mentioned in
this document. Most (if not all) are documented at the start of
<filename>bsd.port.mk</filename>. This file users a non-standard tab
setting. <application>Emacs</application> and
<application>Vim</application> should recognise the setting on loading
the file. Both <command>vi</command> and <command>ex</command> can be
set to use the correct value by typing <command>:set tabstop=4</command>
<para>Only a fraction of the variables
(<makevar><replaceable>VAR</replaceable></makevar>) that can be
overridden are mentioned in this document. Most (if not all) are
documented at the start of <filename>bsd.port.mk</filename>. This
file uses a non-standard tab setting.
<application>Emacs</application> and <application>Vim</application>
should recognise the setting on loading the file. Both
<command>vi</command> and <command>ex</command> can be set to use
the correct value by typing <command>:set tabstop=4</command>
once the file has been loaded.</para>
</note>
@ -1355,7 +1356,7 @@ lib/X11/oneko/mouse.xpm
it in the tree. Your name will also appear in the list of
&ldquo;Additional FreeBSD contributors&rdquo; on the FreeBSD
Handbook and other files. Isn't that great?!? <!-- smiley
-->:)</para>
-->:-)</para>
</sect3>
</sect2>
@ -1377,7 +1378,7 @@ lib/X11/oneko/mouse.xpm
<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>
<!-- smiley --><emphasis>:-&gt;</emphasis></para>
<procedure>
@ -1517,7 +1518,7 @@ lib/X11/oneko/mouse.xpm
by putting it on
<filename>ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/LOCAL_PORTS/</filename>
as the last resort. Please refer to this location as
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports;if
<makevar>MASTER_SITE_LOCAL</makevar>. Send mail to the &a.ports; if
you are not sure what to do.</para>
<para>If your port's distfile changes all the time for no good reason,
@ -1705,7 +1706,7 @@ lib/X11/oneko/mouse.xpm
linkend="porting-categories">categories</link> section for more
discussion about how to pick the right categories.</para>
<para>If you port truly belongs to something that is different from
<para>If your port truly belongs to something that is different from
all the existing ones, you can even create a new category name. In
that case, please send mail to the &a.ports; to propose a new
category.</para>
@ -1802,7 +1803,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<title><makevar>MAINTAINER</makevar></title>
<para>Set your mail-address here. Please. <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
<para>For detailed description of the responsibility of maintainers,
refer to <link linkend="policies-maintainer">MAINTAINER on
@ -2042,7 +2043,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract</programlisting>
<maketarget>install.man</maketarget> target,
<literal>NO_INSTALL_MANPAGES=yes</literal> should be set. In
addition, the author of the original port should be shot. <!--
smiley --><emphasis>:&gt;</emphasis></para>
smiley --><emphasis>:-&gt;</emphasis></para>
<para>If your port's source <filename>Makefile</filename> has
something else than <maketarget>all</maketarget> as the main build
@ -2111,7 +2112,7 @@ lib/libtvl80.so.1
<sect3>
<title>Moving a.out libraries out of the way</title>
<para>A.out libraries should be moved out of
<para>Any a.out libraries should be moved out of
<filename>/usr/local/lib</filename> and similar to an
<filename>aout</filename> subdirectory. (If you do not move them out
of the way, ELF ports will happily overwrite a.out libraries.) The
@ -2298,7 +2299,7 @@ RESOLUTION?= 300
build the port normally.</para>
<para>As for other resolutions, this is the <emphasis>entire</emphasis>
<filename>xdvi118/Makefile</filename>;</para>
<filename>xdvi118/Makefile</filename>:</para>
<programlisting>
RESOLUTION= 118
@ -2758,7 +2759,7 @@ diff -u -r1.15 PLIST
<step>
<para><link linkend="porting-testing">Test</link> and admire your
work. <!-- smiley --><emphasis>:)</emphasis>. Check the
work. <!-- smiley --><emphasis>:-)</emphasis>. Check the
<filename>dir</filename> file before and after each step.</para>
</step>
</procedure>
@ -3253,7 +3254,7 @@ post-install:
</row>
<row>
<entry>2.1-CURRENTs</entry>
<entry>2.1-CURRENT</entry>
<entry>199501, 199503</entry>
</row>
@ -3558,7 +3559,7 @@ post-install:
<filename>bsd.port.mk</filename></title>
<para>Do not write anything after the <literal>.include
&lt;bsd.port.mk&gt;</literal> line. it usually can be avoided by
&lt;bsd.port.mk&gt;</literal> line. It usually can be avoided by
including <filename>bsd.port.pre.mk</filename> somewhere in the
middle of your <filename>Makefile</filename> and
<filename>bsd.port.post.mk</filename> at the end.</para>
@ -4023,7 +4024,7 @@ mysql:*:88:88:MySQL Daemon:/var/db/mysql:/sbin/nologin</programlisting>
<para>Do ask us questions if you have any trouble! Do not just beat
your head against a wall! <!-- smiley
--><emphasis>:)</emphasis></para>
--><emphasis>:-)</emphasis></para>
</sect3>
</sect2>
@ -4789,7 +4790,7 @@ pre-install:
following us to here, really. Now that you know how to do a port,
have at it and convert everything in the world into ports! That
is the easiest way to start contributing to the FreeBSD Project!
<!-- smiley --><emphasis>:)</emphasis></para>
<!-- smiley --><emphasis>:-)</emphasis></para>
</sect2>
</sect1>
</chapter>