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

Diff for /www/Attic/ports.html between version 1.24 and 1.25

version 1.24, 1999/04/23 11:46:31 version 1.25, 1999/09/22 18:56:30
Line 1 
Line 1 
 <html>  <html>
  <head>  <head>
   <meta http-equiv="Content-Type"  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
         content="text/html; charset=iso-8859-1">  <meta name="resource-type" content="document">
   <meta name="resource-type"  <meta name="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">
         content="document">  <meta name="keywords" content="openbsd,ports">
   <meta name="description"  <meta name="distribution" content="global">
         CONTENT="How OpenBSD can make use of the FreeBSD ports">  <meta name="copyright" content="copyright 1997-1999 by the OpenBSD project">
   <meta name="keywords"  
         content="openbsd,ports">  <title>OpenBSD ports mechanism</title>
   <meta name="distribution"  <link rev="made" HREF="mailto:www@openbsd.org">
         content="global">  
   <meta name="copyright"  <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
         content="This document copyright 1997,1998 by the OpenBSD project">  
   <title>OpenBSD ports mechanism</title>  <img height=30 width=141 src=images/smalltitle.gif alt="[OpenBSD]" >
   <link rev="made" HREF="mailto:www@openbsd.org">  <p>
  </head>  <h2><font color=#e00000>OpenBSD ports mechanism</font><hr></h2>
  <body text="#000000" bgcolor="#FFFFFF" link="#23238E">  
   <img height=30 width=141 src=images/smalltitle.gif alt="[OpenBSD]" >  <h3><font color=#0000e0>History</font></h3>
   <h2><font color=#e00000>OpenBSD ports mechanism</font></H2>  
   <h3><font color=#0000e0>History</font></h3>  <p>
   <p>  OpenBSD is a fairly complete system of its own, but still there is a lot
    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
    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
    on where to draw the line as to what to include, as well as the occasional  licensing and export restriction problems.  As OpenBSD is supposed to be
    licensing and export restriction problems.  As OpenBSD is supposed to be  a small stand-alone UNIX-like operating system, some things just can't be
    a small stand-alone UNIX-like operating system, some things just can't be  shipped with the system.
    shipped with the system.  
   <p>  <p>
    We wanted to find a way for users to easily get software we don't provide  We wanted to find a way for users to easily get software we don't provide
    and started to look around. We didn't have to look far, as sibling project  and started to look around. We didn't have to look far, as sibling project
    <a href="http://www.freebsd.org/">FreeBSD</a> already had an  <a href="http://www.freebsd.org/">FreeBSD</a> already had an
         excellent mechanism          excellent mechanism
    for exactly this purpose called  for exactly this purpose called
    <a href="http://www.freebsd.org/ports/">"The ports collection"</a>.  <a href="http://www.freebsd.org/ports/">"The ports collection"</a>.
   <p>  
    At first we tried to use their collection as-is, but due to  <p>
    incompatibility problems between FreeBSD and OpenBSD we decided to branch  At first we tried to use their collection as-is, but due to
    out and create our very own OpenBSD Ports Project using FreeBSD's as a  incompatibility problems between FreeBSD and OpenBSD we decided to branch
    starting point.  This also allows us to tune the ports better to our  out and create our very own OpenBSD Ports Project using FreeBSD's as a
    system.  starting point.  This also allows us to tune the ports better to our
   <h3><font color=#0000e0>Short description and setup</font></h3>  system.
   <p>  
    The ports idea is to have, for each piece of software, a Makefile that  <h3><font color=#0000e0>Short description and setup</font></h3>
    controls  
    <ul>  <p>
     <li>where to fetch it,  The ports idea is to have, for each piece of software, a Makefile that
     <li>how to do the fetch,  controls
     <li>what it depends upon (if anything),  <ul>
     <li>how to alter the sources (if needed),  <li>where to fetch it,
     <li>and how to configure, build and install it.  <li>how to do the fetch,
    </ul>  <li>what it depends upon (if anything),
   <p>  <li>how to alter the sources (if needed),
    This information is kept in a directory hierarchy under the  <li>and how to configure, build and install it.
    /usr/ports directory.  </ul>
   <h3><font color=#0000e0>Getting the Ports tree</font></h3>  <p>
   <p>  This information is kept in a directory hierarchy under the
    The ports source tree can be retrieved via:  /usr/ports directory.
    <ul>  <h3><font color=#0000e0>Getting the Ports tree</font></h3>
     <li><a href=anoncvs.html>Anonymous CVS</a> (see link).  The command is  <p>
          essentially <strong>cvs get ports</strong>.  The ports source tree can be retrieved via:
     <li>Anonymous ftp from  <ul>
         <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz">  <li><a href=anoncvs.html>Anonymous CVS</a> (see link).  The command is
         ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz</a>.  essentially <strong>cvs get ports</strong>.
   <li>Anonymous ftp from
   <a href="ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz">
   ftp://ftp.openbsd.org/pub/OpenBSD/snapshots/ports.tar.gz</a>.
         This archive is updated nightly.          This archive is updated nightly.
     <li>Your web browser using the  <li>Your web browser using the
         <a href="http://www.openbsd.org/cgi-bin/cvsweb/ports/">CVS  <a href="http://www.openbsd.org/cgi-bin/cvsweb/ports/">CVS
         web interface</a>.          web interface</a>.
    </ul>  </ul>
   <p>  <p>
    You can also ftp the latest release version from the pub/OpenBSD/[version]  You can also ftp the latest release version from the pub/OpenBSD/[version]
    (where [version] is the release number, e.g. 2.5) directory  (where [version] is the release number, e.g. 2.5) directory
    on any of the <a href=ftp.html>ftp mirror sites</a>.  on any of the <a href=ftp.html>ftp mirror sites</a>.
    The release versions are the ones we ship on our CDROM, and has gone  The release versions are the ones we ship on our CDROM, and has gone
    through better testing than any snapshot.  However, they age pretty  through better testing than any snapshot.  However, they age pretty
    quickly, due to older distribution files disappearing from the net as  quickly, due to older distribution files disappearing from the net as
    new releases arrive.  Therefore, you likely will want to get and use  new releases arrive.  Therefore, you likely will want to get and use
    a newer version of the ports tree.  a newer version of the ports tree.
   <h3><font color=#0000e0>Example use of the Ports tree</font></h3>  
   <p>  <h3><font color=#0000e0>Example use of the Ports tree</font></h3>
    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  <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
         do something like this:          do something like this:
 <pre>  <pre>
 % cd /usr/ports/archivers/unzip  % cd /usr/ports/archivers/unzip
Line 88 
Line 93 
 # make install  # make install
 # exit  # exit
 </pre>  </pre>
    Easy, huh?  Easy, huh?
   <h3><font color=#0000e0>Port status information</font></h3>  
   <p>  <h3><font color=#0000e0>Port status information</font></h3>
    The <a href="portstat.html">ports status page</a> is updated as  
    team members add new ports and verify existing ports.  Existing  <p>
    ports are continually verified to validate source availability and  The <a href="portstat.html">ports status page</a> is updated as
    proper operation with the current OpenBSD sources.  The page notes  team members add new ports and verify existing ports.  Existing
    the date last checked and the nature of any change.  This is a new  ports are continually verified to validate source availability and
    resource that is not yet complete.  If you have any information to  proper operation with the current OpenBSD sources.  The page notes
    add to the status page please send it to  the date last checked and the nature of any change.  This is a new
    <a href="mailto:ports@openbsd.org">ports@OpenBSD.ORG</a>.  resource that is not yet complete.  If you have any information to
   <h3><font color=#0000e0>Creating new ports</font></h3>  add to the status page please send it to
   <p>  <a href="mailto:ports@openbsd.org">ports@OpenBSD.ORG</a>.
    If you are interested in helping to expand the OpenBSD ports tree  
    you should first read <a href="porting.html">porting.html</a>.  <h3><font color=#0000e0>Creating new ports</font></h3>
    That page references the porting section of the  
    <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>  <p>
    as well as OpenBSD specific policies and hints.  If you are interested in helping to expand the OpenBSD ports tree
   <h3><font color=#0000e0>Problems and contacts</font></h3>  you should first read <a href="porting.html">porting.html</a>.
   <p>  That page references the porting section of the
    If you have trouble with ports please send e-mail to the OpenBSD  <a href="http://www.freebsd.org/handbook/">FreeBSD handbook</a>
    ports mailing list, <a href="mailto:ports@openbsd.org">ports@OpenBSD.ORG</a>.  as well as OpenBSD specific policies and hints.
    Corrections are always welcome, but in any case do please provide:  
    <ul>  <h3><font color=#0000e0>Problems and contacts</font></h3>
     <li>The output of <code>uname -a</code>,  
     <li>Your OpenBSD version, including any patches you may have applied,  <p>
     <li>A complete description of the problem.  If you have trouble with ports please send e-mail to the OpenBSD
    </ul>  ports mailing list, <a href="mailto:ports@openbsd.org">ports@OpenBSD.ORG</a>.
   <hr>  Corrections are always welcome, but in any case do please provide:
  <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>  <ul>
  <a href=mailto:www@openbsd.org>www@openbsd.org</a>  <li>The output of <code>uname -a</code>,
  <br><small>$OpenBSD$</small>  <li>Your OpenBSD version, including any patches you may have applied,
  </body>  <li>A complete description of the problem.
   
   </ul>
   
   <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$</small>
   </body>
 </html>  </html>
Legend:
Removed from v.1.24  
changed lines
  Added in v.1.25