|
Lines 82-88
Link Here
|
| 82 |
|
82 |
|
| 83 |
<para>When this document is not sufficiently detailed, you should |
83 |
<para>When this document is not sufficiently detailed, you should |
| 84 |
refer to <filename>/usr/ports/Mk/bsd.port.mk</filename>, which |
84 |
refer to <filename>/usr/ports/Mk/bsd.port.mk</filename>, which |
| 85 |
all port Makefiles include. Even if you do not hack Makefiles |
85 |
all port <filename>Makefiles</filename> include. |
|
|
86 |
(This is the file that actually |
| 87 |
controls the actual port build process, so if this document says |
| 88 |
one thing and <filename>bsd.port.mk</filename> says another, |
| 89 |
<filename>bsd.port.mk</filename> is correct.) |
| 90 |
Even if you do not hack <filename>Makefiles</filename> |
| 86 |
daily, it is well commented, and you will still gain much |
91 |
daily, it is well commented, and you will still gain much |
| 87 |
knowledge from it. Additionally, you may send specific questions |
92 |
knowledge from it. Additionally, you may send specific questions |
| 88 |
to the &a.ports;.</para> |
93 |
to the &a.ports;.</para> |
|
Lines 4711-4734
Link Here
|
| 4711 |
<para>When you notice that a port is out of date compared to the latest |
4656 |
<para>When you notice that a port is out of date compared to the latest |
| 4712 |
version from the original authors, first make sure you have the latest |
4657 |
version from the original authors, first make sure you have the latest |
| 4713 |
port. You can find them in the |
4658 |
port. You can find them in the |
| 4714 |
<filename>ports/ports-current</filename> directory of the FTP mirror |
4659 |
<filename>ports/ports-current</filename> directory of the FreeBSD FTP mirror |
| 4715 |
sites. You may also use <application>CVSup</application> to keep your whole ports collection |
4660 |
sites. You may also use <application>CVSup</application> to keep your whole ports collection |
| 4716 |
up-to-date, as described in the <ulink url="../handbook/synching.html#CVSUP-CONFIG">Handbook</ulink>.</para> |
4661 |
up-to-date, as described in the <ulink url="../handbook/synching.html#CVSUP-CONFIG">Handbook</ulink>.</para> |
| 4717 |
|
4662 |
|
| 4718 |
<para>The next step is to send an email to the maintainer, if one is |
4663 |
<para>The next step is to send an email to the maintainer, if one is |
| 4719 |
listed in the port's <filename>Makefile</filename>. That person may |
4664 |
listed, in the port's <filename>Makefile</filename>. (Note that |
|
|
4665 |
unmaintained ports are listed under the name of |
| 4666 |
<literal>ports@FreeBSD.org</literal>; mail to that address |
| 4667 |
probably will not help in this case). An active maintainer may |
| 4720 |
already be working on an upgrade, or have a reason to not upgrade the |
4668 |
already be working on an upgrade, or have a reason to not upgrade the |
| 4721 |
port right now (because of, for example, stability problems of the new |
4669 |
port right now (because of, for example, stability problems of the new |
| 4722 |
version).</para> |
4670 |
version), so you will not want to duplicate work in that case.</para> |
| 4723 |
|
4671 |
|
| 4724 |
<para>If the maintainer asks you to do the upgrade or there is not any |
4672 |
<para>If the maintainer asks you to do the upgrade or the maintainer |
| 4725 |
such person to begin with, please make the upgrade and send the |
4673 |
is <literal>ports@FreeBSD.org</literal>, |
| 4726 |
recursive diff (either unified or context diff is fine, but port |
4674 |
please make the upgrade and send the recursive <command>diff</command> |
| 4727 |
committers appear to prefer unified diff more) of the new and old |
4675 |
of the new and old |
| 4728 |
ports directories to us (e.g., if your modified port directory is |
4676 |
ports directories to us (e.g., if your modified port directory is |
| 4729 |
called <filename>superedit</filename> and the original is in our tree |
4677 |
called <filename>superedit</filename> and the original is in our tree |
| 4730 |
as <filename>superedit.bak</filename>, then send us the result of |
4678 |
as <filename>superedit.bak</filename>, then send us the result of |
| 4731 |
<command>diff -ruN superedit.bak superedit</command>). Please examine |
4679 |
<command>diff -ruN superedit.bak superedit</command>). |
|
|
4680 |
Either unified or context diff is fine, but port |
| 4681 |
committers appear to prefer unified diff more. |
| 4682 |
Note the use of the <literal>-N</literal> option—this is |
| 4683 |
the accepted way to force diff to properly deal with the case of |
| 4684 |
new files being added or old files being deleted.</para> |
| 4685 |
|
| 4686 |
<para>Please examine |
| 4687 |
|
| 4732 |
the output to make sure all the changes make sense. The best way to |
4688 |
the output to make sure all the changes make sense. The best way to |
| 4733 |
send us the diff is by including it via &man.send-pr.1; (category |
4689 |
send us the diff is by including it via &man.send-pr.1; (category |
| 4734 |
<literal>ports</literal>). If you are the maintainer for the port, |
4690 |
<literal>ports</literal>). If you are the maintainer for the port, |