[BACK]Return to ports.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/Attic/ports.html between version 1.18 and 1.19

version 1.18, 1998/02/14 10:37:05 version 1.19, 1998/02/15 08:04:25
Line 1 
Line 1 
 <html>  <html>
 <head>   <head>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">    <meta http-equiv="Content-Type"
 <meta name="resource-type" content="document">          content="text/html; charset=iso-8859-1">
 <meta name="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">    <meta name="resource-type"
 <meta name="keywords" content="openbsd,ports">          content="document">
 <meta name="distribution" content="global">    <meta name="description"
 <meta name="copyright" content="This document copyright 1997 by the OpenBSD project">          CONTENT="How OpenBSD can make use of the FreeBSD ports">
 <title>OpenBSD ports mechanism</title>    <meta name="keywords"
 <link rev="made" HREF="mailto:www@openbsd.org">          content="openbsd,ports">
 </head>    <meta name="distribution"
 <body text="#000000" bgcolor="#FFFFFF" link="#23238E">          content="global">
 <img src=images/smalltitle.gif alt="[OpenBSD]" >    <meta name="copyright"
           content="This document copyright 1997,1998 by the OpenBSD project">
 <h2><font color=#e00000>OpenBSD ports mechanism</font></h2>    <title>OpenBSD ports mechanism</title>
     <link rev="made" HREF="mailto:www@openbsd.org">
 <h3><font color=#0000e0>History</font></h3>   </head>
 OpenBSD is a fairly complete system of its own, but still there is a lot   <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
 of software that one might want see added. However there is the problem    <img src=images/smalltitle.gif alt="[OpenBSD]" >
 on where to draw the line as to what to include, as well as the occasional    <h2><font color=#e00000>OpenBSD ports mechanism</font></H2>
 licensing and export restriction problems.    <h3><font color=#0000e0>History</font></h3>
 In what is supposed to be small stand-alone unix-like operating system,    <p>
 some things just can't be shipped with the system.     OpenBSD is a fairly complete system of its own, but still there is a lot
 We wanted to find a way for users to easily get software we don't provide     of software that one might want see added. However there is the problem
 and started to look around. We didn't have to look far as a sibling project,     on where to draw the line as to what to include, as well as the occasional
 <a href="http://www.freebsd.org/">FreeBSD</a>, had an excellent mechanism     licensing and export restriction problems.  In what is supposed to be
 for exactly this purpose called     small stand-alone UNIX-like operating system, some things just can't be
 <a href="http://www.freebsd.org/ports/">"The ports collection"</a>.     shipped with the system.
 At first we tried to use their collection as-is, but due to incompatibility    <p>
 problems between FreeBSD and OpenBSD we decided to branch out and create     We wanted to find a way for users to easily get software we don't provide
 our very own OpenBSD Ports Project using FreeBSD's as a starting point.     and started to look around. We didn't have to look far as a sibling project,
 This also allows us to tune the ports better to our system.     <a href="http://www.freebsd.org/">FreeBSD</a>, had an excellent mechanism
 <h3><font color=#0000e0>Short description and setup</font></h3>     for exactly this purpose called
 The ports idea is to have, for each piece of software, a Makefile that     <a href="http://www.freebsd.org/ports/">"The ports collection"</a>.
 <ul>    <p>
 <li>Describes where to fetch it,     At first we tried to use their collection as-is, but due to
 <li>How to do the fetch,     incompatibility problems between FreeBSD and OpenBSD we decided to branch
 <li>What it is depending upon (if anything),     out and create our very own OpenBSD Ports Project using FreeBSD's as a
 <li>how to alter the sources (if needed),     starting point.  This also allows us to tune the ports better to our
 <li>and how to configure, build and install it.     system.
 </ul>    <h3><font color=#0000e0>Short description and setup</font></h3>
 <p>    <p>
 Normally this information is kept in an hierarchy under /usr/ports     The ports idea is to have, for each piece of software, a Makefile that
 (however, this is configurable).     controls
 <p>     <ul>
 We recommend reading the <a href="http://www.freebsd.org/handbook/ports.html">ports      <li>where to fetch it,
 chapter</a> in the <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>      <li>how to do the fetch,
 to get information on how to setup this hierarchy until OpenBSD can complete      <li>what it depends upon (if anything),
 its own ports.helpfile      <li>how to alter the sources (if needed),
 <h3><font color=#0000e0>Getting the Ports tree</font></h3>      <li>and how to configure, build and install it.
 The ports source tree is available in several ways:     </ul>
 <ul>    <p>
 <li>You can ftp the 2.2 version of it from the pub/OpenBSD/2.2 directory     This information is kept in a directory hierarchy under the
         on any of the <a href=ftp.html>ftp mirror sites</a>.     /usr/ports directory.
 <li>You can use <a href=anoncvs.html>AnonCVS</a> to get the most recent    <h3><font color=#0000e0>Getting the Ports tree</font></h3>
         version of it, using essentially "<strong>cvs get ports</strong>".    <p>
 </ul>     The ports source tree can be retrieved via:
 (Note: the version of the ports tree on the 2.2 CDROM is not the most     <ul>
 recent version.  You likely want to get and use a newer version).      <li><a href=anoncvs.html>Anonymous CVS</a> (see link).  The command is
            essentially <strong>cvs get ports</strong>.
 <h3><font color=#0000e0>Example use of the Ports tree</font></h3>      <li>Anonymous ftp from
 Let's say you managed to get a ports tree sitting under /usr/ports, then          <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz">
 you should be able to something like this:          ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz</a>.
           This archive is updated nightly.
      </ul>
     <p>
      You can also ftp the 2.2 version from the pub/OpenBSD/2.2 directory
      on any of the <a href=ftp.html>ftp mirror sites</a>.
      Note: this version, also on the 2.2 CDROM, is not the most
      recent version.  You likely want to get and use a newer version.
     <h3><font color=#0000e0>Example use of the Ports tree</font></h3>
     <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
      something like:
 <pre>  <pre>
 % cd /usr/ports/archivers/unzip  % cd /usr/ports/archivers/unzip
 % su  % su
Line 68 
Line 80 
 # make install  # make install
 # exit  # exit
 </pre>  </pre>
 Easy, huh?     Easy, huh?
     <h3><font color=#0000e0>Creating new ports</font></h3>
 <h3><font color=#0000e0>Getting ports easily</font></h3>    <p>
 An easy way of getting the ports (at least for now) is by ftp, in     If you are interested in helping to expand the OpenBSD ports tree
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz">pub/OpenBSD/snapshots/ports.tar.gz</a>. It is updated every night.     you should first read <a href="porting.html">porting.html</a>.
      That page references the porting section of the
 <h3><font color=#0000e0>Problems and contacts</font></h3>     <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>
 Our <a href="mailto:joey@openbsd.org">ports coordinator</a> is currently     as well as OpenBSD specific policies and hints.
 working on a ports <a href="http://www.openbsd.org/cgi-bin/cvsweb/ports/">status page.</a>    <h3><font color=#0000e0>Problems and contacts</font></h3>
 <p>    <p>
 If you have trouble with ports contact     Our <a href="mailto:joey@openbsd.org">ports coordinator</a> is currently
 <a href="mailto:joey@openbsd.org">Ejovi Nuwere</a> (preferably),     working on a port
 <a href="mailto:gene@openbsd.org">Gene Skonicki</a>, or     <a href="http://www.openbsd.org/cgi-bin/cvsweb/ports/">status page.</a>
 <a href="mailto:todd@openbsd.org">Todd Tyrone Fries</a>.    <p>
 <p>     If you have trouble with ports please send mail to the OpenBSD
 Please provide either patches or enough details for repair, if you     ports mailing list, <a href="mailto:ports@openbsd.org">ports@OpenBSD.ORG</a>.
 cannot do this, point us at the problematic port and tell us what     Patches are always appreciated, but in any case please provide:
 fails and we shall try to fix it.     <ul>
       <li>The output of <code>uname -a</code>
 <hr>      <li>Your OpenBSD version, including any patches you may have applied.
 <a href="index.html"><img src=back.gif border=0 alt=OpenBSD></a>      <li>A complete description of the problem.
 <a href=mailto:www@openbsd.org>www@openbsd.org</a>     </ul>
 <br><small>$OpenBSD$</small>    <hr>
    <a href="index.html"><img src=back.gif border=0 alt=OpenBSD></a>
 </body>   <a href=mailto:www@openbsd.org>www@openbsd.org</a>
    <br><small>$OpenBSD$</small>
    </body>
 </html>  </html>
Legend:
Removed from v.1.18  
changed lines
  Added in v.1.19