=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v retrieving revision 1.29 retrieving revision 1.30 diff -c -r1.29 -r1.30 *** www/Attic/ports.html 1999/10/25 07:45:55 1.29 --- www/Attic/ports.html 2000/05/27 14:51:26 1.30 *************** *** 13,19 **** [OpenBSD] !

Ports and Packages

History

--- 13,22 ---- [OpenBSD] !

OpenBSD ports tree is currently tracking OpenBSD 2.7 ! (release)

!
!

Ports and Packages

History

*************** *** 63,79 **** ftp mirror sites. The release versions are the ones we ship on our CDROM, and have gone through more testing than any snapshot.

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, ! you might want to get and use a newer version of the ports tree. ! Please note that the ports-current tree is tested with OpenBSD-current and is ! NOT guaranteed to work with the previous stable release. ! It is strongly suggested that people don't track ports-current unless ! they're prepared to track the whole of OpenBSD-current, including source. Mailing lists such as source-changes or tech will probably be invaluable. --- 66,116 ---- ftp mirror sites. The release versions are the ones we ship on our CDROM, and have gone through more testing than any snapshot. +

+ Further information is available in the + ports(7) man page. +

Ports versus packages

+

+ 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: +

+ OpenBSD documentation includes more information on the proper use of + packages. + +

Ports update for an OpenBSD release

+ +

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 (But this ! specific problem should be solved now). ! !

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

! !

! The change of status will be widely publicized on the ! Mailing lists. ! !

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. ! !

It is strongly suggested that people don't track ports-current unless ! they're prepared to deal with various problems. Mailing lists such as source-changes or tech will probably be invaluable. *************** *** 106,111 **** --- 143,149 ---- Easy, huh? +

Creating new ports

*************** *** 143,148 ****
OpenBSD www@openbsd.org !
$OpenBSD: ports.html,v 1.29 1999/10/25 07:45:55 espie Exp $ --- 182,187 ----
OpenBSD www@openbsd.org !
$OpenBSD: ports.html,v 1.30 2000/05/27 14:51:26 espie Exp $