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

More wordsmithing.

Browse source 
Submitted by:	linimon
PR:		docs/53424
This commit is contained in:
Ceri Davies 2004-01-19 00:15:45 +00:00
parent 77b32e5746
commit 5f57ec7515
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=19736
1 changed files with 20 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -16,6 +16,8 @@
%teams;
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mailing-lists;
<!ENTITY % freebsd PUBLIC "-//FreeBSD//ENTITIES DocBook Miscellaneous FreeBSD Entities//EN">
%freebsd;
]>
@ -4573,7 +4575,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
<para>When you notice that a port is out of date compared to the latest
version from the original authors, first make sure you have the latest
port. You can find them in the
<filename>ports/ports-current</filename> directory of the FTP mirror
<filename>ports/ports-current</filename> directory of the &os; FTP mirror
sites. You may also use <application>CVSup</application> to keep your whole ports collection
up-to-date, as described in the <ulink url="../handbook/synching.html#CVSUP-CONFIG">Handbook</ulink>.</para>
@ -4581,16 +4583,27 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
listed in the port's <filename>Makefile</filename>. That person may
already be working on an upgrade, or have a reason to not upgrade the
port right now (because of, for example, stability problems of the new
version).</para>
version); you would not want to duplicate their work. Note that
unmaintained ports are listed with a maintainer of
<literal>ports@FreeBSD.org</literal>; mail to that address
probably will not help in this case.</para>
<para>If the maintainer asks you to do the upgrade or there is not any
such person to begin with, please make the upgrade and send the
recursive diff (either unified or context diff is fine, but port
committers appear to prefer unified diff more) of the new and old
<para>If the maintainer asks you to do the upgrade or the maintainer
is <literal>ports@FreeBSD.org</literal>,
please make the upgrade and send the
recursive <command>diff</command> output
of the new and old
ports directories to us (e.g., if your modified port directory is
called <filename>superedit</filename> and the original is in our tree
as <filename>superedit.bak</filename>, then send us the result of
<command>diff -ruN superedit.bak superedit</command>). Please examine
<command>diff -ruN superedit.bak superedit</command>). Either
unified or context diff is fine, but port committers generally
prefer unified diffs. Note the use of the <literal>-N</literal>
option&mdash;this is the accepted way to force diff to properly
deal with the case of new files being added or old files being
deleted.</para>
<para>Please examine
the output to make sure all the changes make sense. The best way to
send us the diff is by including it via &man.send-pr.1; (category
<literal>ports</literal>). If you are the maintainer for the port,