www/ports.html - diff

Return to ports.html CVS log

Up to [local] / www

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

version 1.9, 1997/11/23 04:09:47

version 1.10, 1997/11/30 14:15:35

Line 19

<B>History</B></H3>

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

on where to draw the line on what to include and not, as well as licensing

on where to draw the line on what to include and not in a small unix-like

and export restrictions problems. Some things just can't be shipped with

operating system, as well as licensing and export restrictions problems.

the system. We wanted to find a way for users to easily get software we

Some things just can't be shipped with the system.

don't provide and started to look around. We didn't have to look far as

We wanted to find a way for users to easily get software we don't provide

a sibling project, <A HREF="http://www.freebsd.org/">FreeBSD</A>, had an

and started to look around. We didn't have to look far as a sibling project,

excellent mechanism for exactly this purpose called <A HREF="http://www.freebsd.org/ports/">"The

<A HREF="http://www.freebsd.org/">FreeBSD</A>, had an excellent mechanism

ports collection"</A>. After thinking about it for a while we decided to

for exactly this purpose called <A HREF="http://www.freebsd.org/ports/">"The

try to use their collection as is, but do incompatibility problems between

ports collection"</A>.

FreeBSD and OpenBSD we decided to branch out and create our very own OpenBSD

After thinking about it for a while we decided to try to use their

collection as is, but due to incompatibility problems between FreeBSD

and OpenBSD we decided to branch out and create our very own OpenBSD

Ports Project using FreeBSD's as a starting point.

<BR> 

<H3>

Line 38

Line 40

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

(however, this is configurable).

<p>

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>

to get information on how to setup this hierarchy until OpenBSD can complete

its on ports.helpfile

its own ports.helpfile

<H3>

<B>Example</B></H3>

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

<PRE>

make

% cd /usr/ports/archivers/unzip

% make

make install

% su

exit

# make install

# exit

</PRE>

Easy, huh?

<H3>

<B>Problems and contacts</B></H3>

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

right now, on what architecture, etc. If you have trouble with ports contact

right now, on what architecture, etc.

either <A HREF="mailto:joey@openbsd.org">Ejovi Nuwere</A> (preferably),

If you have trouble with ports contact either

<A HREF="mailto:gene@openbsd.org">Gene Skonicki</A> or <A

<A HREF="mailto:joey@openbsd.org">Ejovi Nuwere</A> (preferably),

HREF="mailto:todd@openbsd.org">Todd Tyrone Fries</A> and give us either patches on

<A HREF="mailto:gene@openbsd.org">Gene Skonicki</A>, or

how to fix things or, if you cannot

<A HREF="mailto:todd@openbsd.org">Todd Tyrone Fries</A>

do this, point us at the problematic port and tell us what fails and we

and provide either patches or details for how to fix things or,

shall try to fix it.

if you cannot do this, point us at the problematic port and tell

us what fails and we shall try to fix it.

<BR>

<A HREF="mailto:www@openbsd.org">www@openbsd.org</A>