Add text to the Dealing With Broken Ports sectino. First, direct people

to GNATS instead of the mailing lists or the Porter's Handbook.  Also
provide links to the How To Write Problem Reports article, the mailing
list article, and the mirror list.  Finally, add text trying to explain
the difference between maintained and unmaintained ports.

Glanced over by:	simon
This commit is contained in:
Mark Linimon 2005-09-18 07:54:55 +00:00
parent 341bef6be3
commit 56f9a51317
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=25691

View file

@ -1314,6 +1314,13 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
there are a few things you can do, including:</para> there are a few things you can do, including:</para>
<orderedlist> <orderedlist>
<listitem>
<para>Find out if there is a fix pending for the port in
the <ulink url="&url.base;/support.html#gnats">Problem Report
database</ulink>. If so, you may be able to use the
proposed fix.</para>
</listitem>
<listitem> <listitem>
<para>Fix it! The <ulink <para>Fix it! The <ulink
url="&url.books.porters-handbook;/index.html">Porter's url="&url.books.porters-handbook;/index.html">Porter's
@ -1323,17 +1330,35 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</listitem> </listitem>
<listitem> <listitem>
<para>Gripe&mdash;<emphasis>by email only</emphasis>! Send <para>Ask the maintainer of the port for help. Type
email to the maintainer of the port first. Type
<command>make maintainer</command> or read the <command>make maintainer</command> or read the
<filename>Makefile</filename> to find the maintainer's <filename>Makefile</filename> to find the maintainer's
email address. Remember to include the name and version email address. Remember to include the name and version
of the port (send the <literal>&dollar;FreeBSD:</literal> of the port (send the <literal>&dollar;FreeBSD:</literal>
line from the <filename>Makefile</filename>) and the line from the <filename>Makefile</filename>) and the
output leading up to the error when you email the output leading up to the error when you email the
maintainer. If you do not get a response from the maintainer.</para>
maintainer, you can use &man.send-pr.1; to submit a bug
report.</para> <note>
<para>Some ports are not maintained by an individual but
instead by a <ulink
url="&url.articles.mailing-list-faq;/article.html">mailing
list</ulink>. Many, but not all, of these addresses look like
<literal>freebsd-listname@FreeBSD.org</literal>. Please
take this into account when phrasing your questions.</para>
<para>In particular, ports shown as maintained by
<literal>freebsd-ports@FreeBSD.org</literal> are
actually not maintained by anyone. Fixes and support, if
any, come from the general community who subscribe to that
mailing list. More volunteers are always needed!</para>
</note>
<para>If you do not get a response,
you can use &man.send-pr.1; to submit a bug
report (see <ulink
url="&url.articles.problem-reports;/article.html">Writing
FreeBSD Problem Reports</ulink>).</para>
</listitem> </listitem>
<listitem> <listitem>
@ -1341,7 +1366,8 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
<quote>master</quote> package collection is on <hostid <quote>master</quote> package collection is on <hostid
role="fqdn">ftp.FreeBSD.org</hostid> in the <ulink role="fqdn">ftp.FreeBSD.org</hostid> in the <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages
directory</ulink>, but be sure to check your local mirror directory</ulink>, but be sure to check your <ulink
url="http://mirrorlist.FreeBSD.org/">local mirror</ulink>
<emphasis>first</emphasis>! These are more likely to work <emphasis>first</emphasis>! These are more likely to work
than trying to compile from source and are a lot faster as than trying to compile from source and are a lot faster as
well. Use the &man.pkg.add.1; program to install the well. Use the &man.pkg.add.1; program to install the