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

[ports committer:] clean up some unclear language left behind by ceri's

Browse source 
recent commit of some patches of mine.  No new text, just more clarity.

PR:			docs/61653 (partial)
Reviewed by:		ceri
Approved by:		ceri
This commit is contained in:
Mark Linimon 2004-01-20 23:49:53 +00:00
parent f9eed73b3b
commit f0e56c628f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=19762
1 changed files with 12 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -64,7 +64,7 @@
<chapter id="own-port">
<title>Making a port yourself</title>
<para>So, you are still interested in making your own port or
<para>So, you are interested in making your own port or
upgrading an existing one? Great!</para>
<para>What follows are some guidelines for creating a new port for
@ -769,7 +769,7 @@ lib/X11/oneko/mouse.xpm
<listitem>
<para>Addition of patches to correct security
vulnerabilities, bugs, or to add new functionality to
the FreeBSD port.</para>
the port.</para>
</listitem>
<listitem>
@ -832,7 +832,7 @@ lib/X11/oneko/mouse.xpm
the changes do not introduce any functional change on
any other platforms on which the port did previously
build). Since <makevar>PORTREVISION</makevar> reflects
the content of the package, if no package was
the content of the package, if the package was not
previously buildable then there is no need to increase
<makevar>PORTREVISION</makevar> to mark a
change.</para>
@ -1577,7 +1577,7 @@ PORTEPOCH= 1</programlisting>
safely delete <literal>misc</literal> and just put the port
in that other subdirectory! If at all possible, try to
find a better category for your port than
<literal>misc</literal> ports tend to get overlooked
<literal>misc</literal>, as ports tend to get overlooked
in here.</entry>
</row>
@ -1938,7 +1938,7 @@ PORTEPOCH= 1</programlisting>
<para><makevar>DISTNAME</makevar> is the name of the port as
called by the authors of the software.
<makevar>DISTNAME</makevar> defaults to
<literal>${PORTNAME}-${PORTVERSION}</literal>, so override it if necessary.
<literal>${PORTNAME}-${PORTVERSION}</literal>, so override it only if necessary.
<makevar>DISTNAME</makevar> is only used in two places.
First, the distribution file list
(<makevar>DISTFILES</makevar>) defaults to
@ -1950,7 +1950,7 @@ PORTEPOCH= 1</programlisting>
<note>
<para><makevar>PKGNAMEPREFIX</makevar> and
<makevar>PKGNAMESUFFIX</makevar> do not affect
<makevar>DISTNAME</makevar>. Also note that when
<makevar>DISTNAME</makevar>. Also note that if
<makevar>WRKSRC</makevar> is equal to
<filename>work/<makevar>${PORTNAME}-${PORTVERSION}</makevar></filename>
while the original source archive is named something other than
@ -1997,7 +1997,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>These variables are defined in
<filename>/usr/ports/Mk/bsd.sites.mk</filename>. There are
new archives added all the time, so make sure to check the
new entries added all the time, so make sure to check the
latest version of this file before submitting a port.</para>
<para>The user can also set the <makevar>MASTER_SITE_*</makevar>
@ -3440,7 +3440,7 @@ LDCONFIG_DIRS= %%PREFIX%%/lib/foo %%PREFIX%%/lib/bar</programlisting>
package is not generally useful, and the application should always
be compiled from the source code. For example, if the application
has configuration information that is site specific hard coded in to
it at compile time.</para>
it at compile time, set <makevar>NO_PACKAGE</makevar>.</para>
<para><makevar>NO_PACKAGE</makevar> should be set to a string
describing the reason why the package should not be
@ -4547,7 +4547,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
occurrences of <filename>/usr/local</filename> (or
<filename>/usr/X11R6</filename> for X ports that do not use imake)
in the various <filename>scripts/Makefile</filename>s in the port to read
<makevar>PREFIX</makevar>, as this variable is automatically passed
<makevar>${PREFIX}</makevar>, as this variable is automatically passed
down to every stage of the build and install processes.</para>
<para>Make sure your application is not installing things in
@ -4557,7 +4557,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<screen>&prompt.root; <userinput>make clean; make package PREFIX=/var/tmp/<replaceable>port-name</replaceable></userinput></screen>
<para>If anything is installed outside of <makevar>PREFIX</makevar>,
making the package creation process will complain that it
the package creation process will complain that it
cannot find the files.</para>
<!-- XXX This paragraph is confusing and poorly indented. -->
@ -6397,8 +6397,8 @@ bacula:*:910:910:Bacula Daemon:/var/db/bacula:/sbin/nologin</programlisting>
number of vulnerable FreeBSD hosts (we like being known
for being secure), however sometimes there is a
noticeable time gap between disclosure of a
vulnerability and an updated software release of a piece
of vulnerable software. Do not mark a port
vulnerability and an updated release of the
vulnerable software. Do not mark a port
<makevar>FORBIDDEN</makevar> for any reason other than
security.</para>
</listitem>