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

Fxi assorted typos.

Browse source
This commit is contained in:
Tim Vanderhoek 1999-01-01 12:15:49 +00:00
parent 62a00af744
commit 5183595dde
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=4004
1 changed files with 20 additions and 20 deletions

40
handbook/porting.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: porting.sgml,v 1.119 1998-12-12 07:09:09 asami Exp $ -->
<!-- $Id: porting.sgml,v 1.120 1999-01-01 12:15:49 hoek Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Making a port yourself<label id="porting"></heading>
@ -103,7 +103,7 @@ A cat chasing a mouse all over the screen.
<tt>README</tt> or manpage</em>; too often they are not a
concise description of the port or are in an awkward format
(e.g. manpages have justified spacing). If the ported software
has an official WWW homepage, you should list in here.
has an official WWW homepage, you should list it here.
<p>It is recommended that you sign the name at the end of
this file, as in:
@ -311,7 +311,7 @@ lib/X11/oneko/mouse.xpm
</enum>
<item>The build target is run. This is responsible for
descending into the ports' private working directory
descending into the port's private working directory
(<tt>&dollar;{WRKSRC}</tt>) and building it. If
<tt>&dollar;{USE_GMAKE}</tt> is set, GNU <tt>make</tt>
will be used, otherwise the system <tt>make</tt> will be
@ -345,7 +345,7 @@ lib/X11/oneko/mouse.xpm
<p>Note that the `main' targets (e.g., <tt>extract</tt>,
<tt>configure</tt>, etc.) do nothing more than make sure all
the stages up to that one is completed and call the real
the stages up to that one are completed and call the real
targets or scripts, and they are not intended to be
changed. If you want to fix the extraction, fix
<tt>do-extract</tt>, but never ever touch <tt>extract</tt>!
@ -392,7 +392,7 @@ ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/LOCAL_PORTS/
<p>If your port requires some additional `patches' that are
available on the Internet, fetch them too and put them in
<tt>&dollar;{DISTDIR}</tt>. Do not worry if they come from
site other than where you got the main source tarball,
a site other than where you got the main source tarball,
we have a way to handle these situations (see the
description of <ref id="porting:patchfiles"
name="&dollar;{PATCHFILES}"> below).
@ -615,7 +615,7 @@ MASTER_SITE_SUBDIR= applications
(i.e., <tt>&dollar;{WKRSRC}</tt>) because it contains some
extra pathnames, set <tt>&dollar;{PATCH_DIST_STRIP}</tt>
accordingly. For instance, if all the pathnames in the
patch has an extra `<tt>foozolix-1.0/</tt>' in front of the
patch have an extra `<tt>foozolix-1.0/</tt>' in front of the
filenames, then set `<tt>PATCH_DIST_STRIP=-p1</tt>'.
<p>Do not worry if the patches are compressed, they will be
@ -821,7 +821,7 @@ BUILD_DEPENDS= /nonexistent:${PORTSDIR}/graphics/jpeg:extract
the behavior you want can be accomplished. It will cause
the other port to be always built (and installed, by
default), and the dependency will go into the package as
well. If this is really what you need, I recommend you to
well. If this is really what you need, I recommend you
write it as <tt/BUILD_DEPENDS/ and <tt/RUN_DEPENDS/
instead -- at least the intention will be clear.
@ -1057,7 +1057,7 @@ ${SETENV} OBJFORMAT=${PORTOBJFORMAT} ${LDCONFIG} -m ....
part of <tt><ref id="porting:pkgname" name="PKGNAME"></tt>
so the packages will have different names.
<p>This will be best demostrated by an example. This is
<p>This will be best demonstrated by an example. This is
part of <tt>japanese/xdvi300/Makefile</tt>:
<tscreen><verb>
:
@ -1516,8 +1516,8 @@ diff -u -r1.15 PLIST
<sect2>
<heading><tt/INSTALL/</heading>
<p>If your port needs execute commands when the binary package
is installed with <tt/pkg_add/ you can do with via the pkg/INSTALL
<p>If your port needs to execute commands when the binary package
is installed with <tt/pkg_add/ you can do this via the pkg/INSTALL
script. This script will automatically be added to the
package, and will be run twice by pkg_add. The first time
will as `<tt>INSTALL &dollar;{PKGNAME} PRE-INSTALL</tt>'
@ -1529,7 +1529,7 @@ diff -u -r1.15 PLIST
for additional information.
Note, that this script is not run automatically if you install
the port with `<tt>make install</tt>'. If you are depending
on it being run, you will have to explicitly call it on your
on it being run, you will have to explicitly call it from your
port's Makefile.
<sect2>
@ -1595,7 +1595,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}
same <tt/pkg/ subdirectory among several ports or have to
write to one of the above files (see <ref
id="porting:wrkdir" name="writing to places other than
WRKDIR"> for why it is a bad idea to write directry into the
WRKDIR"> for why it is a bad idea to write directly into the
<tt/pkg/ subdirectory).
<p>Here is a list of variable names and their default values.
@ -1621,7 +1621,7 @@ PKGMESSAGE ${PKGDIR}/MESSAGE
<p>Some software packages have restrictive licenses or can be in
violation to the law (PKP's patent on public key crypto,
ITAR (export of crypto software) to name just two of them).
What we can do with them vary a lot, depending on the exact
What we can do with them varies a lot, depending on the exact
wordings of the respective licenses.
<p>Note that it is your responsibility as a porter to read the
@ -1793,7 +1793,7 @@ PKGMESSAGE ${PKGDIR}/MESSAGE
</verb></tscreen>
<p>to the proper place in the <tt>.c</tt> file. We believe that every
system that defines these to symbols has sys/param.h. If you find
system that defines these two symbols has sys/param.h. If you find
a system that doesn't, we would like to know. Please send
mail to the &a.ports;.
@ -1830,7 +1830,7 @@ PKGMESSAGE ${PKGDIR}/MESSAGE
The value of the BSD macro is 199506 for the 4.4BSD-Lite2 code
base. This is stated for informational purposes only. It should
not be used to distinguish between version of FreeBSD based only
not be used to distinguish between versions of FreeBSD based only
on 4.4-Lite vs. versions that have merged in changes from 4.4-Lite2.
The __FreeBSD__ macro should be used instead.
@ -1938,7 +1938,7 @@ PKGMESSAGE ${PKGDIR}/MESSAGE
<descrip>
<tag>&dollar{ARCH}</tag> The archetecture, as returned by
<tag>&dollar{ARCH}</tag> The architecture, as returned by
`<tt>uname -m</tt>' (e.g., `i386').
<tag>&dollar{OPSYS}</tag> The operating system type, as returned by
@ -2007,7 +2007,7 @@ post-install:
port to be installed at the same time, you
can use the whole <tt>&dollar;{PKGNAME}</tt>.
<p>Make the installation dependent to the variable
<p>Make the installation dependent on the variable
<tt>NOPORTDOCS</tt> so that users can disable it in
<tt>/etc/make.conf</tt>, like this:
<tscreen><verb>
@ -2135,9 +2135,9 @@ post-install:
`<tt>sbin</tt>' (executables for superusers/managers),
`<tt>info</tt>' (documentation for info browser) or
`<tt>share</tt>' (architecture independent files). See man
<tt>hier(7)</tt> for details, the rule governing
<tt>/usr</tt> pretty much applies to <tt>/usr/local</tt>
too. The exception are ports dealing with USENET `news'.
<tt>hier(7)</tt> for details; the rules governing
<tt>/usr</tt> pretty much apply to <tt>/usr/local</tt>
too. The exceptions are ports dealing with USENET `news'.
They may use <tt>&dollar;{PREFIX}/news</tt> as a destination
for their files.