===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -c -r1.13 -r1.14
*** www/Attic/ports.html	1997/11/30 14:31:46	1.13
--- www/Attic/ports.html	1997/11/30 14:42:39	1.14
***************
*** 14,21 ****
  
  <h2>OpenBSD ports mechanism</H2>
  
! <h3>
! <b>History</b></h3>
  OpenBSD is a fairly complete system of its own, but still there is a lot
  of software that one might want see added. However there is the problem
  on where to draw the line as to what to include, as well as the occasional
--- 14,20 ----
  
  <h2>OpenBSD ports mechanism</H2>
  
! <h3>History</h3>
  OpenBSD is a fairly complete system of its own, but still there is a lot
  of software that one might want see added. However there is the problem
  on where to draw the line as to what to include, as well as the occasional
***************
*** 31,38 ****
  problems between FreeBSD and OpenBSD we decided to branch out and create
  our very own OpenBSD Ports Project using FreeBSD's as a starting point.
  This also allows us to tune the ports better to our system.
! <h3>
! <b>Short description and setup</b></h3>
  The ports idea is to have, for each piece of software, a Makefile that
  <ul>
  <li>Describes where to fetch it,
--- 30,36 ----
  problems between FreeBSD and OpenBSD we decided to branch out and create
  our very own OpenBSD Ports Project using FreeBSD's as a starting point.
  This also allows us to tune the ports better to our system.
! <h3>Short description and setup</h3>
  The ports idea is to have, for each piece of software, a Makefile that
  <ul>
  <li>Describes where to fetch it,
***************
*** 49,56 ****
  chapter</a> in the <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>
  to get information on how to setup this hierarchy until OpenBSD can complete
  its own ports.helpfile
! <h3>
! <b>Example</b></h3>
  Let's say you managed to get a ports tree sitting under /usr/ports, then
  you should be able to something like this:
  <pre>
--- 47,64 ----
  chapter</a> in the <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>
  to get information on how to setup this hierarchy until OpenBSD can complete
  its own ports.helpfile
! <h3>Getting the Ports tree</h3>
! The ports source tree is available in several ways:
! <ul>
! <li>You can ftp the 2.2 version of it from the pub/OpenBSD/2.2 directory
! 	on any of the <a href=ftp.html>ftp mirror sites</a>.
! <li>You can use <a href=anoncvs.html>AnonCVS</a> to get the most recent
! 	version of it, using essentially "<strong>cvs get ports</strong>".
! </ul>
! (Note: the version of the ports tree on the 2.2 CDROM is not the most
! recent version.  You likely want to get and use a newer version).
! 
! <h3>Example use of the Ports tree</h3>
  Let's say you managed to get a ports tree sitting under /usr/ports, then
  you should be able to something like this:
  <pre>
***************
*** 61,68 ****
  # exit
  </pre>
  Easy, huh?
! <h3>
! <b>Problems and contacts</b></h3>
  Our <a href="mailto:joey@openbsd.org">ports coordinator</a> is currently
  working on a ports status page.
  <p>
--- 69,75 ----
  # exit
  </pre>
  Easy, huh?
! <h3>Problems and contacts</h3>
  Our <a href="mailto:joey@openbsd.org">ports coordinator</a> is currently
  working on a ports status page.
  <p>
***************
*** 78,84 ****
  <hr>
  <a href="index.html"><img 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.13 1997/11/30 14:31:46 deraadt Exp $</small>
  
  </body>
  </html>
--- 85,91 ----
  <hr>
  <a href="index.html"><img 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.14 1997/11/30 14:42:39 deraadt Exp $</small>
  
  </body>
  </html>