ports.html web page

[Heikki Korpela <heko@iki.fi>]

Hi list, would this look reasonable? Hopefully, it would help
decrease the traffic on the list, and sync ports.html a bit
with /usr/ports/README.

Index: ports.html
===================================================================
RCS file: /cvs/www/ports.html,v
retrieving revision 1.53
diff -I'$Id' -u -b -B -p -r1.53 ports.html
--- ports.html  2001/07/27 23:42:52     1.53
+++ ports.html  2001/08/06 20:10:23
@@ -228,6 +228,10 @@ ports tree.
 <h3><font color="#0000e0">Example Use of the Ports Tree</font></h3>

 <p>
+First, please read the <pre>/usr/ports/README</pre> file on your system.
+</p>
+
+<p>
 Let's say you managed to get a ports tree and you want to compile and
 install the archiving utility <strong>unzip</strong>.  You should be able to
        do something like this:
@@ -277,9 +281,17 @@ as well as OpenBSD specific policies and
 <h3><font color="#0000e0"><a name="Help">Problems and Contacts</a></font></h3>

 <p>
-If you have trouble with existing ports, or need information about creating 
new ports,
-please send e-mail to the OpenBSD
+If you have trouble with an existing port, please send e-mail to the
+port maintainer. To see who is the maintainer of the port, type, for
+example:
+<pre>
+       % cd /usr/ports/archivers/unzip
+       % make show VARNAME=MAINTAINER
+</pre>
+Alternatively, if there is no maintainer, or you can't reach
+him/her, send mail to the OpenBSD
 ports mailing list, <a href="mailto:ports@openbsd.org";>ports@openbsd.org</a>.
+Please don't use the misc@openbsd.org mailing list for questions about ports.
 Corrections are always welcome, but in any case do please provide:
 <ul>
 <li>The output of <code>uname -a</code>,
@@ -287,8 +299,24 @@ Corrections are always welcome, but in a
 <li>A complete description of the problem.
 </ul>
 For ports that don't build correctly, a complete build transcript is almost
-always required. Some ports may have configuration issues linked to what
-is already on your machine.
+always required. You can use the portslogger script, found in
+/usr/ports/infrastructure/build, for this. A sample run of portslogger
+might be:
+
+<pre>
+       % cd /usr/ports/archivers/unzip
+       % su
+       # mkdir -p ~/portslogs
+       # make clean install 2>&1 | /usr/ports/infrastructure/build/portslogger 
\
+               ~/portslogs
+</pre>
+
+After this, you should have a logfile of the build in your ~/portslogs 
directory
+that you can send to the port maintainer. Also, make sure you are not using
+any special options in your build, for example in /etc/mk.conf.
+
+<p>
+Alternatively, you can
 <ul>
 <li>Use <a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=script&amp;sektion=1&amp;format=html";>script(1)</a>
 to create a complete build transcript. Don't remove the configure information.
     <li>Attach the output of <a 
href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&amp;sektion=1&amp;format=html";>pkg_info(1)</a>
 if it seems even remotely relevant.