===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- www/Attic/ports.html	2001/08/06 21:57:18	1.54
+++ www/Attic/ports.html	2001/08/12 20:14:29	1.55
@@ -28,6 +28,8 @@
 <li><a href="#Use">Using Ports</a></li>
 <li><a href="#Life">Life Cycle of the Ports Tree</a></li>
 <li><a href="#XFree86">Ports and XFree86</a></li>
+<li><a href="#Example">Example Use of the Ports Tree</a></li>
+<li><a href="#Advanced">Advanced Usage of the Ports Tree</a></li>
 <li><a href="#Create">Creating New Ports</a></li>
 <li><a href="#Help">Problems and Contacts</a></li>
 </ul>
@@ -67,7 +69,8 @@
 
 <p>
 Packages are the binary equivalent of ports.  A compiled port becomes
-a package that can be registered into the system using pkg_add(1).
+a package that can be registered into the system using 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>
 
 <p>
 <strong><font color="#e00000">
@@ -184,7 +187,8 @@
 The current ports tree <strong>may not</strong> be used with the previous
 release once the switch to tracking OpenBSD-current occurs.  This is due
 to changes, typically with the port make process, that require code
-based upon the OpenBSD-current source tree.   
+based upon the OpenBSD-current source tree. This switch will be announced
+on the <a href="mail.html"><tt>ports@openbsd.org</tt> mailing list</a>.
 <p>The ports tree works as a single entity. Updating a single directory is
 not guaranteed to work, as package dependencies may force you to update
 and recompile vast portions of the ports tree.
@@ -225,13 +229,9 @@
 to a default binary XFree86 4.0.x distribution for it to work with the OpenBSD
 ports tree.
 
-<h3><font color="#0000e0">Example Use of the Ports Tree</font></h3>
+<h3><a name="Example"></a><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:
@@ -262,7 +262,8 @@
 <p>
 As ports get built, the /usr/ports/distfiles directory gets filled with 
 program sources, and /usr/ports/packages gets filled with binary packages.  
-Users with low connectivity may refer to mirror-distfiles(7) for 
+Users with low connectivity may refer to 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mirroring-ports&sektion=7&format=html">mirroring-ports(7)</a> for
 an efficient way to grab all distfiles at once.  In OpenBSD-current, you 
 can use the script /usr/ports/infrastructure/fetch/clean-old to track
 old distfiles.
@@ -270,6 +271,19 @@
 If you wish to have the distfiles, you will have to get them through an
 independent way.
 
+<h3><font color="#0000e0"><a name="Advanced"></a>Advanced Usage of the Ports Tree</font></h3>
+
+<p>
+Ports tree has many features for the advanced user that make it a valuable
+tool beyond basic installation. Advanced users may wish to tamper with
+the makefiles (you should read the 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=make&sektion=1&format=html">make(1)</a>
+manual page first) or set various variables from the make commandline or in 
+<tt>/etc/mk.conf</tt>. These variables are described in detail in the
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=bsd.port.mk&sektion=5&format=html">bsd.port.mk(5)</a>
+manual page, and the porting documents below.
+</p>
+
 <h3><font color="#0000e0"><a name="Create">Creating New Ports</a></font></h3>
 <p>
 If you are interested in helping to expand the OpenBSD ports tree
@@ -328,6 +342,6 @@
 <hr>
 <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a> 
 <a href="mailto:www@openbsd.org">www@openbsd.org</a>
-<br><small>$OpenBSD: ports.html,v 1.54 2001/08/06 21:57:18 lebel Exp $</small>
+<br><small>$OpenBSD: ports.html,v 1.55 2001/08/12 20:14:29 heko Exp $</small>
 </body>
 </html>