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

Diff for /www/Attic/ports.html between version 1.8 and 1.9

version 1.8, 1997/11/18 08:12:33 version 1.9, 1997/11/23 04:09:47
Line 1 
Line 1 
 <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">  
 <HTML>  <HTML>
   <HEAD>  <HEAD>
     <TITLE>     <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
       OpenBSD ports mechanism     <META NAME="resource-type" CONTENT="document">
     </TITLE>     <META NAME="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">
     <LINK REV="made" HREF="mailto:www@openbsd.org">     <META NAME="keywords" CONTENT="openbsd,ports">
     <META NAME="resource-type" CONTENT="document">     <META NAME="distribution" CONTENT="global">
     <META NAME="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">     <META NAME="copyright" CONTENT="This document copyright 1997 by the OpenBSD project">
     <META NAME="keywords" CONTENT="openbsd,ports">     <META NAME="GENERATOR" CONTENT="Mozilla/4.03 [en] (Win95; I) [Netscape]">
     <META NAME="distribution" CONTENT="global">     <TITLE>OpenBSD ports mechanism</TITLE>
     <META NAME="copyright" CONTENT="This document copyright 1997 by the OpenBSD project">  <LINK REV="made" HREF="mailto:www@openbsd.org">
   </HEAD>  </HEAD>
   <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">  <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#23238E">
     <IMG ALT="[OpenBSD]" SRC="images/smalltitle.gif">  <IMG SRC="http://www.openbsd.org/images/smalltitle.gif" ALT="[OpenBSD]" >
     <H2>OpenBSD ports mechanism</H2>  <H2>
     <P>  OpenBSD ports mechanism</H2>
     <H3><STRONG>History</STRONG></H3>  
     <P>  <H3>
       OpenBSD is a fairly complete system of its own, but still there is a lot of  <B>History</B></H3>
       software that one might want see added.  However there is the problem on where  OpenBSD is a fairly complete system of its own, but still there is a lot
       to draw the line on what to include and not, as well as licensing and export  of software that one might want see added. However there is the problem
       restrictions problems.  Some things just can't be shipped with the system.  on where to draw the line on what to include and not, as well as licensing
       We wanted to find a way for users to easily get software we don't provide  and export restrictions problems. Some things just can't be shipped with
       and started to look around.  We didn't have to look far as a sibling project,  the system. We wanted to find a way for users to easily get software we
       <A HREF="http://www.freebsd.org/">FreeBSD</A>, had an excellent mechanism for  don't provide and started to look around. We didn't have to look far as
       exactly this purpose called  a sibling project, <A HREF="http://www.freebsd.org/">FreeBSD</A>, had an
       <A HREF="http://www.freebsd.org/ports/">"The ports collection"</A>.  After  excellent mechanism for exactly this purpose called <A HREF="http://www.freebsd.org/ports/">"The
       thinking about it for a while we decided to try to use their collection as is,  ports collection"</A>. After thinking about it for a while we decided to
       feeding back necessary patches to make the ports work on OpenBSD as well  try to use their collection as is, but do incompatibility problems between
       to the FreeBSD maintainers.  FreeBSD and OpenBSD we decided to branch out and create our very own OpenBSD
     </P>  Ports Project using FreeBSD's as a starting point.
     <H3><STRONG>Short description and setup</STRONG></H3>  <BR>&nbsp;
     <P>  <H3>
       The ports idea is to have, for each piece of software, a Makefile that  <B>Short description and setup</B></H3>
       describes where to fetch it, how to do the fetch, what it is depending upon  The ports idea is to have, for each piece of software, a Makefile that
       (if anything), how to alter the sources (if needed) and how to configure,  describes where to fetch it, how to do the fetch, what it is depending
       build and install it.  Furthermore some patches will have to be kept in the  upon (if anything), how to alter the sources (if needed) and how to configure,
       "port" as well as some administration files for the package registry utilities.  build and install it. Furthermore some patches will have to be kept in
       Normally this information is kept in an hierarchy under /usr/ports (however,  the "port" as well as some administration files for the package registry
       this is configurable).  I recommend reading the  utilities. Normally this information is kept in an hierarchy under /usr/ports
       <A HREF="http://www.freebsd.org/handbook/ports.html">ports chapter</A> in the  (however, this is configurable). I recommend reading the <A HREF="http://www.freebsd.org/handbook/ports.html">ports
       <A HREF="http://www.freebsd.org/handbook/">FreeBSD handbook</A> to get  chapter</A> in the <A HREF="http://www.freebsd.org/handbook/">FreeBSD handbook</A>
       information on how to setup this hierarchy.  A current gzipped tar-archive  to get information on how to setup this hierarchy until OpenBSD can complete
       of the FreeBSD ports can be found  its on ports.helpfile
       <A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports.tar.gz">here  <H3>
       </A>.  <B>Example</B></H3>
     </P>  Let's say you managed to get a ports tree sitting under /usr/ports, then
     <H3><STRONG>Example</STRONG></H3>  you should be able to something like this:
     <P>  <PRE>cd /usr/ports/archivers/unzip
       Let's say you managed to get a ports tree sitting under /usr/ports, then you  
       should be able to something like this:  
     <PRE>  
 cd /usr/ports/archivers/unzip  
 make  make
 su  su
 make install  make install
 exit  exit
     </PRE>  </PRE>
     Easy, huh?  Easy, huh?
   </P>  <H3>
     <H3><STRONG>Problems and contacts</STRONG></H3>  <B>Problems and contacts</B></H3>
     <P>  Our <A HREF="mailto:joey@openbsd.org">ports coordinator</A> is currently
       As the ports collection really is a FreeBSD thing, there are ports that do not  working on a ports statues page - what is done, what is being worked on
       work in OpenBSD for various reasons.  But this is going to change in the near future.  right now, on what architecture, etc. If you have trouble with ports contact
       Our <A HREF="mailto:joey@openbsd.org">ports coordinator</A> has set up a  either <A HREF="mailto:joey@openbsd.org">Ejovi Nuwere</A> (preferably),
       <A HREF="http://deeplaid.uni-svishtov.bg/ports-status.html">page with the current status</A>  <A HREF="mailto:gene@openbsd.org">Gene Skonicki</A> or <A
       - what is done, what is being worked on right now, on what architecture, etc.  HREF="mailto:todd@openbsd.org">Todd Tyrone Fries</A> and give us either patches on
       If you have trouble with ports contact either  how to fix things or, if you cannot
       <A HREF="mailto:joey@openbsd.org">Ejovi Nuwere</A> (preferably),  do this, point us at the problematic port and tell us what fails and we
       <A HREF="mailto:niklas@openbsd.org">Niklas Hallqvist</A> or  shall try to fix it.
       <A HREF="mailto:imp@openbsd.org">Warner Losh</A> and give us either patches  <BR>
       on how to fix things or, if you cannot do this, point us at the problematic  <HR><A HREF="http://www.openbsd.org/index.html"><IMG SRC="http://www.openbsd.org/back.gif" ALT="OpenBSD" BORDER=0 ></A>
       port and tell us what fails and we shall try to fix it.  <A HREF="mailto:www@openbsd.org">www@openbsd.org</A>
     </P>  <BR><FONT SIZE=-1>$OpenBSD: ports.html,v 1.8 1997/11/18 08:12:33 deraadt
     <HR>  Exp $</FONT>
     <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.8  
changed lines
  Added in v.1.9