[BACK]Return to ports.html CVS log [TXT][DIR] Up to [local] / www
File: [local] / www / Attic / ports.html (download) (as text)

Revision 1.4, Fri Jun 13 02:22:28 1997 UTC (26 years, 11 months ago) by downsj
Branch: MAIN
Changes since 1.3: +5 -3 lines 

Make all of the top level pages more consistent.

Now for the rest...

<!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">
<html>
<head>
<title>OpenBSD ports mechanism</title>
<link rev=made href=mailto:www@openbsd.org>
<meta name="resource-type" content="document">
<meta name="description" content="How OpenBSD can make use of the FreeBSD ports">
<meta name="keywords" content="openbsd,ports">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 1997 by the OpenBSD project">
</head>

<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">

<img alt="[OpenBSD]" SRC="images/smalltitle.gif">

<h2>OpenBSD ports mechanism</h2>

<p>
<h3><strong>History</strong></h3>

<p>
OpenBSD is a fairly complete system of its own, but still there are a lot 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, as well as licensing and export
restrictions problems.  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
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 for
exactly this purpose called
<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 collection as is,
feeding back necessary patches to make the ports work on OpenBSD as well
to the FreeBSD maintainers.
</p>

<h3><strong>Short description and setup</strong></h3>

<p>
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 upon
(if anything), how to alter the sources (if needed) and how to configure,
build and install it.  Furthermore some patches will have to be kept in the
"port" as well as some administration files for the package registry utilities.
Normally this information is kept in an hierarchy under /usr/ports (however,
this is configurable).  I 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> to get
information on how to setup this hierarchy.  A current gzipped tar-archive
of the FreeBSD ports can be found
<a href=ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports.tar.gz>here
</a>.
</p>

<h3><strong>Example</strong></h3>

<p>
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
su
make install
exit
</pre>
Easy, huh?
</p>

<h3><strong>Problems and contacts</strong></h3>

<p>
As the ports collection really is a FreeBSD thing, there are ports that do not
work in OpenBSD for various reasons.  If you find such a port contact either
<a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a> or
<a href=mailto:imp@openbsd.org>Warner Losh</a> and give us either patches
on how to fix things or, if you cannot do this, point us at the problematic
port and tell us what fails and we shall try to fix it.
</p>

<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.4 1997/06/13 02:22:28 downsj Exp $</small>

</body>
</html>