| version 1.4, 1997/06/13 02:22:28 |
version 1.5, 1997/09/17 11:14:21 |
|
|
| <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN"> |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN"> |
| <html> |
<HTML> |
| <head> |
<HEAD> |
| <title>OpenBSD ports mechanism</title> |
<TITLE> |
| <link rev=made href=mailto:www@openbsd.org> |
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"> |
| </head> |
<META NAME="distribution" CONTENT="global"> |
| |
<META NAME="copyright" CONTENT="This document copyright 1997 by the OpenBSD project"> |
| <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E"> |
</HEAD> |
| |
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E"> |
| <img alt="[OpenBSD]" SRC="images/smalltitle.gif"> |
<IMG ALT="[OpenBSD]" SRC="bsdsoft.gif"> |
| |
<H2>OpenBSD ports mechanism</H2> |
| <h2>OpenBSD ports mechanism</h2> |
<P> |
| |
<H3><STRONG>History</STRONG></H3> |
| <p> |
<P> |
| <h3><strong>History</strong></h3> |
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 |
| <p> |
to draw the line on what to include and not, as well as licensing and export |
| OpenBSD is a fairly complete system of its own, but still there are a lot of |
restrictions problems. Some things just can't be shipped with the system. |
| software that one might want see added. However there is the problem on where |
We wanted to find a way for users to easily get software we don't provide |
| to draw the line on what to include and not, as well as licensing and export |
and started to look around. We didn't have to look far as a sibling project, |
| restrictions problems. Some things just can't be shipped with the system. |
<A HREF="http://www.freebsd.org/">FreeBSD</A>, had an excellent mechanism for |
| We wanted to find a way for users to easily get software we don't provide |
exactly this purpose called |
| and started to look around. We didn't have to look far as a sibling project, |
<A HREF="http://www.freebsd.org/ports/">"The ports collection"</A>. After |
| <a href=http://www.freebsd.org/>FreeBSD</a>, had an excellent mechanism for |
thinking about it for a while we decided to try to use their collection as is, |
| exactly this purpose called |
feeding back necessary patches to make the ports work on OpenBSD as well |
| <a href=http://www.freebsd.org/ports/>"The ports collection"</a>. After |
to the FreeBSD maintainers. |
| thinking about it for a while we decided to try to use their collection as is, |
</P> |
| feeding back necessary patches to make the ports work on OpenBSD as well |
<H3><STRONG>Short description and setup</STRONG></H3> |
| to the FreeBSD maintainers. |
<P> |
| </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 |
| <h3><strong>Short description and setup</strong></h3> |
(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 |
| <p> |
"port" as well as some administration files for the package registry utilities. |
| The ports idea is to have, for each piece of software, a Makefile that |
Normally this information is kept in an hierarchy under /usr/ports (however, |
| describes where to fetch it, how to do the fetch, what it is depending upon |
this is configurable). I recommend reading the |
| (if anything), how to alter the sources (if needed) and how to configure, |
<A HREF="http://www.freebsd.org/handbook/ports.html">ports chapter</A> in the |
| build and install it. Furthermore some patches will have to be kept in the |
<A HREF="http://www.freebsd.org/handbook/">FreeBSD handbook</A> to get |
| "port" as well as some administration files for the package registry utilities. |
information on how to setup this hierarchy. A current gzipped tar-archive |
| Normally this information is kept in an hierarchy under /usr/ports (however, |
of the FreeBSD ports can be found |
| this is configurable). I recommend reading the |
<A HREF="ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports.tar.gz">here |
| <a href=http://www.freebsd.org/handbook/ports.html>ports chapter</a> in the |
</A>. |
| <a href=http://www.freebsd.org/handbook/>FreeBSD handbook</a> to get |
</P> |
| information on how to setup this hierarchy. A current gzipped tar-archive |
<H3><STRONG>Example</STRONG></H3> |
| of the FreeBSD ports can be found |
<P> |
| <a href=ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-current/ports.tar.gz>here |
Let's say you managed to get a ports tree sitting under /usr/ports, then you |
| </a>. |
should be able to something like this: |
| </p> |
<PRE> |
| |
|
| <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 |
cd /usr/ports/archivers/unzip |
| make |
make |
| su |
su |
| make install |
make install |
| exit |
exit |
| </pre> |
</PRE> |
| Easy, huh? |
Easy, huh? |
| </p> |
</P> |
| |
<H3><STRONG>Problems and contacts</STRONG></H3> |
| <h3><strong>Problems and contacts</strong></h3> |
<P> |
| |
As the ports collection really is a FreeBSD thing, there are ports that do not |
| <p> |
work in OpenBSD for various reasons. But this is going to change in the near future. |
| As the ports collection really is a FreeBSD thing, there are ports that do not |
Our <A HREF="mailto:tacho@openbsd.org">ports coordinator</A> has set up a |
| work in OpenBSD for various reasons. If you find such a port contact either |
<A HREF="http://deeplaid.uni-svishtov.bg/ports-status.html">page with the current status</A> |
| <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a> or |
- what is done, what is being worked on right now, on what architecture, etc. |
| <a href=mailto:imp@openbsd.org>Warner Losh</a> and give us either patches |
If you have trouble with ports contact either |
| on how to fix things or, if you cannot do this, point us at the problematic |
<A HREF="mailto:tacho@openbsd.org">Stanislav Grozev</A> (preferably), |
| port and tell us what fails and we shall try to fix it. |
<A HREF="mailto:niklas@openbsd.org">Niklas Hallqvist</A> or |
| </p> |
<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 |
| <hr> |
port and tell us what fails and we shall try to fix it. |
| <a href=index.html><img src=back.gif border=0 alt=OpenBSD></a> |
</P> |
| <a href=mailto:www@openbsd.org>www@openbsd.org</a> |
<HR> |
| <br> |
<A HREF="index.html"><IMG SRC="back.gif" BORDER="0" ALT="OpenBSD"></A> |
| <small>$OpenBSD$</small> |
<A HREF="mailto:www@openbsd.org">www@openbsd.org</A> |
| |
<BR> |
| </body> |
<SMALL>$OpenBSD$</SMALL> |
| </html> |
</BODY> |
| |
</HTML> |
![[BACK]](/icons/back.gif){kind=icon}
Return to ports.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www