www/ports.html - diff

Return to ports.html CVS log

Up to [local] / www

Diff for /www/Attic/ports.html between version 1.29 and 1.30

version 1.29, 1999/10/25 07:45:55

version 1.30, 2000/05/27 14:51:26

Line 13

<p>

<center><h2><font color=#e00000>OpenBSD ports tree is currently tracking OpenBSD 2.7

(release)</font></h2></center>

<hr>

<h2><font color=#e00000>Ports and Packages</font><hr></h2>

<h3><font color=#0000e0>History</font></h3>

Line 63

Line 66

<a href=ftp.html>ftp mirror sites</a>.

The release versions are the ones we ship on our CDROM, and have gone

through more testing than any snapshot.

<p>

Further information is available in the

<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ports&sektion=7&format=html">ports(7)</a> man page.

<h3><font color=#0000e0>Ports versus packages</font></h3>

<p>

For common architectures, you don't necessarily have to compile anything

in the ports tree. With the advent of OpenBSD 2.7, a large set of

pre-compiled packages will be available:

<ul>

<li>On the CD-Rom (that you can pre-order <a href="orders.html">here</a>),

<li>On the ftp mirrors.

</ul>

OpenBSD documentation includes more information on the proper use of

<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=packages&sektion=7&format=html">packages</a>.

<h3><font color=#0000e0>Ports update for an OpenBSD release</font></h3>

<p>

The ports tree, like the rest of OpenBSD, is constantly changing. While

we try to maintain ports compatibility through the lifetime of a particular

release, sometimes issues beyond our control occur. For example, particular

versions of the ported package might no longer be available. Therefore,

versions of the ported package might no longer be available (But this

you might want to get and use a newer version of the ports tree.

specific problem should be solved now).

Please note that the ports-current tree is tested with OpenBSD-current and is

<strong>NOT</strong> guaranteed to work with the previous stable release.

<p>

It is strongly suggested that people don't track ports-current unless

The normal life cycle of the ports tree is as follows:

they're prepared to track the whole of OpenBSD-current, including source.

<ul>

<li>Track the latest release of OpenBSD for a few months after the release

comes out.

<li>Switch to tracking OpenBSD-current about two months before the next

release.

</ul>

<p>

The change of status will be widely publicized on the

<a href=mail.html>Mailing lists</a>.

<p>The ports tree works as a single entity. Updating a single directory is

not guaranteed to work, as package dependencies may force you to update

and recompile vast portions of the ports tree.

<p>It is strongly suggested that people don't track ports-current unless

they're prepared to deal with various problems.

<a href=mail.html>Mailing lists</a> such as source-changes or tech will

probably be invaluable.

Line 106

Line 143

</pre>

Easy, huh?

<!--

<h3><font color=#0000e0>Port status information</font></h3>

<p>

Line 117

Line 155

yet complete. If you have any information to add to the status page

please send it to

<a href="mailto:ports@openbsd.org">ports@openbsd.org</a>.

-->

<h3><font color=#0000e0>Creating new ports</font></h3>