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

Diff for /www/Attic/ports.html between version 1.10 and 1.11

version 1.10, 1997/11/30 14:15:35 version 1.11, 1997/11/30 14:25:33
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" content="text/html; charset=iso-8859-1">
    <META NAME="resource-type" CONTENT="document">  <meta name="resource-type" content="document">
    <META NAME="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">  <meta name="description" CONTENT="How OpenBSD can make use of the FreeBSD ports">
    <META NAME="keywords" CONTENT="openbsd,ports">  <meta name="keywords" content="openbsd,ports">
    <META NAME="distribution" CONTENT="global">  <meta name="distribution" content="global">
    <META NAME="copyright" CONTENT="This document copyright 1997 by the OpenBSD project">  <meta name="copyright" content="This document copyright 1997 by the OpenBSD project">
    <META NAME="GENERATOR" CONTENT="Mozilla/4.03 [en] (Win95; I) [Netscape]">  <title>OpenBSD ports mechanism</title>
    <TITLE>OpenBSD ports mechanism</TITLE>  <link rev="made" HREF="mailto:www@openbsd.org">
 <LINK REV="made" HREF="mailto:www@openbsd.org">  </head>
 </HEAD>  <body text="#000000" bgcolor="#FFFFFF" link="#23238E">
 <BODY TEXT="#000000" BGCOLOR="#FFFFFF" LINK="#23238E">  <img src="http://www.openbsd.org/images/smalltitle.gif" alt="[OpenBSD]" >
 <IMG SRC="http://www.openbsd.org/images/smalltitle.gif" ALT="[OpenBSD]" >  
 <H2>  
 OpenBSD ports mechanism</H2>  
   
 <H3>  <h2>OpenBSD ports mechanism</H2>
 <B>History</B></H3>  
   <h3>
   <b>History</b></h3>
 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 on what to include and not in a small unix-like  on where to draw the line as to what to include, as well as the occasional
 operating system, as well as licensing and export restrictions problems.  licensing and export restriction problems.
 Some things just can't be shipped with the system.  In what is supposed to be small stand-alone unix-like operating system,
   some things just can't be shipped with the system.
 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 a sibling project,  and started to look around. We didn't have to look far as a sibling project,
 <A HREF="http://www.freebsd.org/">FreeBSD</A>, had an excellent mechanism  <a href="http://www.freebsd.org/">FreeBSD</a>, had an excellent mechanism
 for exactly this purpose called <A HREF="http://www.freebsd.org/ports/">"The  for exactly this purpose called
 ports collection"</A>.  <a href="http://www.freebsd.org/ports/">"The ports collection"</a>.
 After thinking about it for a while we decided to try to use their  At first we tried to use their collection as-is, but due to incompatibility
 collection as is, but due to incompatibility problems between FreeBSD  problems between FreeBSD and OpenBSD we decided to branch out and create
 and OpenBSD we decided to branch out and create our very own OpenBSD  our very own OpenBSD Ports Project using FreeBSD's as a starting point.
 Ports Project using FreeBSD's as a starting point.  This also allows us to tune the ports better to our system.
 <BR>&nbsp;  <br>&nbsp;
 <H3>  <h3>
 <B>Short description and setup</B></H3>  <b>Short description and setup</b></h3>
 The ports idea is to have, for each piece of software, a Makefile that  The ports idea is to have, for each piece of software, a Makefile that
 describes where to fetch it, how to do the fetch, what it is depending  <ul>
 upon (if anything), how to alter the sources (if needed) and how to configure,  <li>Describes where to fetch it,
 build and install it. Furthermore some patches will have to be kept in  <li>How to do the fetch,
 the "port" as well as some administration files for the package registry  <li>What it is depending upon (if anything),
 utilities. Normally this information is kept in an hierarchy under /usr/ports  <li>how to alter the sources (if needed),
   <li>and how to configure, build and install it.
   </ul>
   <p>
   Normally this information is kept in an hierarchy under /usr/ports
 (however, this is configurable).  (however, this is configurable).
 <p>  <p>
 We recommend reading the <A HREF="http://www.freebsd.org/handbook/ports.html">ports  We recommend reading the <a href="http://www.freebsd.org/handbook/ports.html">ports
 chapter</A> in the <A HREF="http://www.freebsd.org/handbook/">FreeBSD handbook</A>  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  to get information on how to setup this hierarchy until OpenBSD can complete
 its own ports.helpfile  its own ports.helpfile
 <H3>  <h3>
 <B>Example</B></H3>  <b>Example</b></h3>
 Let's say you managed to get a ports tree sitting under /usr/ports, then  Let's say you managed to get a ports tree sitting under /usr/ports, then
 you should be able to something like this:  you should be able to something like this:
 <PRE>  <pre>
 % cd /usr/ports/archivers/unzip  % cd /usr/ports/archivers/unzip
 % make  % make
 % su  % su
 # make install  # make install
 # exit  # exit
 </PRE>  </pre>
 Easy, huh?  Easy, huh?
 <H3>  <h3>
 <B>Problems and contacts</B></H3>  <b>Problems and contacts</b></h3>
 Our <A HREF="mailto:joey@openbsd.org">ports coordinator</A> is currently  Our <a href="mailto:joey@openbsd.org">ports coordinator</a> is currently
 working on a ports statues page - what is done, what is being worked on  working on a ports status page.
 right now, on what architecture, etc.  <p>
 If you have trouble with ports contact either  If you have trouble with ports contact
 <A HREF="mailto:joey@openbsd.org">Ejovi Nuwere</A> (preferably),  <a href="mailto:joey@openbsd.org">Ejovi Nuwere</a> (preferably),
 <A HREF="mailto:gene@openbsd.org">Gene Skonicki</A>, or  <a href="mailto:gene@openbsd.org">Gene Skonicki</a>, or
 <A HREF="mailto:todd@openbsd.org">Todd Tyrone Fries</A>  <a href="mailto:todd@openbsd.org">Todd Tyrone Fries</a>.
 and provide either patches or details for how to fix things or,  <p>
 if you cannot do this, point us at the problematic port and tell  Please provide either patches or enough details for repair, if you
 us what fails and we shall try to fix it.  cannot do this, point us at the problematic port and tell us what
 <BR>  fails and we shall try to fix it.
 <HR><A HREF="http://www.openbsd.org/index.html"><IMG SRC="http://www.openbsd.org/back.gif" ALT="OpenBSD" BORDER=0 ></A>  
 <A HREF="mailto:www@openbsd.org">www@openbsd.org</A>  <hr>
 <BR><FONT SIZE=-1>$OpenBSD: ports.html,v 1.8 1997/11/18 08:12:33 deraadt  <a href="index.html"><img src=back.gif border=0 alt=OpenBSD></a>
 Exp $</FONT>  <a href=mailto:www@openbsd.org>www@openbsd.org</a>
 </BODY>  <br><small>$OpenBSD$</small>
 </HTML>  
   </body>
   </html>
Legend:
Removed from v.1.10  
changed lines
  Added in v.1.11