OpenBSD Ports and Packages

=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/Attic/ports.html,v retrieving revision 1.46 retrieving revision 1.47 diff -c -r1.46 -r1.47 *** www/Attic/ports.html 2000/12/18 03:21:41 1.46 --- www/Attic/ports.html 2001/02/18 15:23:35 1.47 *************** *** 1,23 **** ! ! OpenBSD Ports and Packages !

The Ports & Packages collection

Motivation

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 as to what to include, as well as the occasional --- 1,26 ---- + ! ! OpenBSD Ports and Packages !

The Ports & Packages collection

Motivation

+ 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 as to what to include, as well as the occasional *************** *** 26,32 **** shipped with the system.

! The ports & packages collection does NOT go through the thorough security audit that OpenBSD follows. Although we strive to keep the quality of the packages collection high, we just do not have enough human resources to ensure the same level of robustness and security. --- 29,35 ---- shipped with the system.

! Packages look like simple .tgz bundles, but they should always be added using ! pkg_add(1), as there might be some extra information that only ! pkg_add(1) knows how to handle. Tip: you can distinguish between packages and .tgz bundles using ! pkg_info(1). !

Getting packages

A large collection of pre-compiled packages is available for most common architectures. --- 55,72 ---- a package that can be registered into the system using pkg_add(1).
! Packages look like simple .tgz bundles, but they should always be added using ! pkg_add(1), as there might be some extra information that only ! pkg_add(1) knows how to handle. Tip: you can distinguish between packages and .tgz bundles using ! pkg_info(1). !
Getting packages
A large collection of pre-compiled packages is available for most common architectures. *************** *** 92,98 **** # pkg_add ${PKG_PATH}gimp-1.1.27.tgz !
Ports and packages update for an OpenBSD release

The 2.7 release saw the introduction of a stable branch for the ports tree.
--- 95,101 ---- # pkg_add ${PKG_PATH}gimp-1.1.27.tgz !
Ports and packages update for an OpenBSD release

The 2.7 release saw the introduction of a stable branch for the ports tree.
*************** *** 116,124 **** and a bug-fixed package.
!
Managing installed packages
! The packages(7) manual page holds useful information about ways to manage installed packages, solve conflicts (files that already exist) and handle dependencies. --- 119,127 ---- and a bug-fixed package.
!
Managing installed packages
! The packages(7) manual page holds useful information about ways to manage installed packages, solve conflicts (files that already exist) and handle dependencies. *************** *** 126,139 **** As of OpenBSD 2.8, to update a package you must:

Remove the old package using ! pkg_delete(1)
Add the new package using ! pkg_add(1)
This is slightly inconvenient, as packages may trigger dependencies, and you may have to remove a large subset of packages for an update. !
Using ports
If a given package does not exist for your architecture, you may still be able to compile the port. Besides, some users will want to compile --- 129,142 ---- As of OpenBSD 2.8, to update a package you must:

Remove the old package using ! pkg_delete(1)
Add the new package using ! pkg_add(1)
This is slightly inconvenient, as packages may trigger dependencies, and you may have to remove a large subset of packages for an update. !
Using ports
If a given package does not exist for your architecture, you may still be able to compile the port. Besides, some users will want to compile *************** *** 146,154 **** 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. !
Life cycle of the ports tree

The ports tree, like the rest of OpenBSD, is constantly changing. --- 149,157 ---- 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. !
Life cycle of the ports tree

The ports tree, like the rest of OpenBSD, is constantly changing. *************** *** 160,166 **** release. The change of status will be widely publicized on the ! Mailing lists.
The current ports tree may not be used with the previous --- 163,169 ---- release. The change of status will be widely publicized on the ! mailing lists.
The current ports tree may not be used with the previous *************** *** 173,181 **** 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@openbsd.org or tech@openbsd.org will probably be invaluable.
The ports-current tree can be retrieved via:
--- 176,187 ---- It is strongly suggested that people don't track ports-current unless they're prepared to deal with various problems. Mailing lists such as ! ports-changes@openbsd.org or tech@openbsd.org will probably be invaluable. +
A list of daily changes to ports + and ports-current is available. +
The ports-current tree can be retrieved via:
*************** *** 192,198 **** web interface.
!
Ports and XFree
There is some special magic in the OpenBSD XFree configuration files that allows the ports tree to install imake-based applications under /usr/local. --- 198,204 ---- web interface.
!
Ports and XFree
There is some special magic in the OpenBSD XFree configuration files that allows the ports tree to install imake-based applications under /usr/local. *************** *** 205,211 **** ports tree.
Future releases of XFree 4.0.x will probably include the necessary magic. !
Example use of the Ports tree

Let's say you managed to get a ports tree and you want to compile and --- 211,217 ---- ports tree.
Future releases of XFree 4.0.x will probably include the necessary magic. !
Example use of the Ports tree

Let's say you managed to get a ports tree and you want to compile and *************** *** 246,252 **** If you wish to have the distfiles, you will have to get them through an independent way. !
Creating new ports

If you are interested in helping to expand the OpenBSD ports tree you should first read porting.html. --- 252,258 ---- If you wish to have the distfiles, you will have to get them through an independent way. !
Creating new ports

If you are interested in helping to expand the OpenBSD ports tree you should first read porting.html. *************** *** 254,260 **** FreeBSD handbook as well as OpenBSD specific policies and hints. !
Problems and contacts

If you have trouble with existing ports, or need information about creating new ports, --- 260,266 ---- FreeBSD handbook as well as OpenBSD specific policies and hints. !
Problems and contacts

If you have trouble with existing ports, or need information about creating new ports, *************** *** 270,285 **** always required. Some ports may have configuration issues linked to what is already on your machine.
!
Use script(1) to create a complete build transcript. Don't remove the configure information. !
Attach the output of pkg_info(1) if it seems even remotely relevant. !
gcc(1) internal compiler errors do ask you to report the bug to the gcc mailing-list. It does save time if you follow their direction, and provide at least the various files produced by gcc -save-temps.

! www@openbsd.org !
$OpenBSD: ports.html,v 1.46 2000/12/18 03:21:41 espie Exp $ --- 276,291 ---- always required. Some ports may have configuration issues linked to what is already on your machine.
!
Use script(1) to create a complete build transcript. Don't remove the configure information. !
Attach the output of pkg_info(1) if it seems even remotely relevant. !
gcc(1) internal compiler errors do ask you to report the bug to the gcc mailing-list. It does save time if you follow their direction, and provide at least the various files produced by gcc -save-temps.

! www@openbsd.org !
$OpenBSD: ports.html,v 1.47 2001/02/18 15:23:35 naddy Exp $