===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- www/Attic/ports.html	2000/06/15 16:48:50	1.32
+++ www/Attic/ports.html	2000/06/17 15:13:00	1.33
@@ -53,10 +53,15 @@
 
 <p>
 <strong><font color=#e00000>
-Packages look like simple <code>.tar.gz</code> bundles, but they should always
-be added using pkg_add(1), as there might be some extra information that only
-pkg_add(1) knows how to handle.</font></strong>
-Tip: you can distinguish between packages and .tar.gz bundles using pkg_info(1).
+Packages look like simple <code>.tar.gz</code> bundles, but they should 
+always be added using 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a>, 
+as there might be some extra information that only
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a> 
+knows how to handle.</font></strong>
+Tip: you can distinguish between packages and <strong>.tar.gz</strong> bundles 
+using 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_info&sektion=1&format=html">pkg_info(1)</a>.
 
 <h3><font color=#0000e0>Getting packages</font></h3>
 
@@ -78,20 +83,22 @@
 
 <pre>
     # setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/
-    # pkg_add gimp-1.17.tar.gz
+    # pkg_add gimp-1.1.17.tar.gz
 </pre>
 
 <h3><font color=#0000e0>Managing installed packages</font></h3>
 
-The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>.
+The <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages(7)</a>
 manual page holds useful information about ways to manage
 installed packages, solve conflicts (files that already exist) and handle
 dependencies.
 <p>
 As of OpenBSD 2.7, to update a package you must:
 <ul>
-<li>Remove the old package using pkg_delete(1)
-<li>Add the new package using pkg_add(1)
+<li>Remove the old package using 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_delete&sektion=1&format=html">pkg_delete(1)</a> 
+<li>Add the new package using 
+<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pkg_add&sektion=1&format=html">pkg_add(1)</a> 
 </ul>
 This is slightly inconvenient, as packages may trigger dependencies, and 
 you may have to remove a large subset of packages for an update.
@@ -130,8 +137,9 @@
 and recompile vast portions of the ports tree.
 It is strongly suggested that people don't track ports-current unless
 they're prepared to deal with various problems.
-<a href=mail.html>Mailing lists</a> such as source-changes or tech will
-probably be invaluable.
+<a href=mail.html>Mailing lists</a> such as
+<code>source-changes@openbsd.org</code> or
+<code>tech@openbsd.org</code> will probably be invaluable.
 
 <p>
 The ports-current tree can be retrieved via:
@@ -153,7 +161,7 @@
 
 <p>
 Let's say you managed to get a ports tree and you want to compile and
-install the archiving utility <code>unzip</code>.  You should be able to
+install the archiving utility <strong>unzip</strong>.  You should be able to
 	do something like this:
 
 <pre>
@@ -214,6 +222,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.32 2000/06/15 16:48:50 naddy Exp $</small>
+<br><small>$OpenBSD: ports.html,v 1.33 2000/06/17 15:13:00 espie Exp $</small>
 </body>
 </html>