![[OpenBSD]](images/smalltitle.gif){kind=small}
- 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 --- 13,23 ----
! ! We wanted to find a way for users to easily get software we don't provide ! and started to look around. We didn't have to look far, as sibling project ! FreeBSD already had an ! excellent mechanism ! for exactly this purpose called ! "The ports collection".
! At first we tried 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. This also allows us to tune the ports better to our ! system. ! !
! The ports idea is to have, for each piece of software, a Makefile that controls
! ! 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. !
! The port collection, originally borrowed from ! FreeBSD, fills this gap. ! The concept is to have, for each third-party software, a Makefile that controls
This information is kept in a directory hierarchy under the /usr/ports directory. !
! You can ftp the release version from the pub/OpenBSD/[version] (where ! [version] is the release number) directory on any of the ! 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. !
! 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:
! 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:
! Packages are the binary equivalent of ports. A compiled port becomes ! a package that can be registered into the system using pkg_add(1). !
!
! Packages look like simple .tar.gz 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 .tar.gz bundles using pkg_info(1).
!
pkg_add pkgname.tar.gz.
! If you are grabbing packages off a single source (a package repository),
! set PKG_PATH to that repository URL.
! For instance, to install the gimp package for the 2.7 release on an i386 ! machine off the ftp site (including dependencies), do: +
+ # setenv PKG_PATH ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/ + # pkg_add gimp-1.17.tar.gz ++ +
+ As of OpenBSD 2.7, to update a package you must: +
+ You can ftp the release version from the pub/OpenBSD/[version] (where + [version] is the release number) directory on any of the + 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. + +
+ The ports tree, like the rest of OpenBSD, is constantly changing. 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. --- 122,134 ----
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.
***************
*** 134,164 ****
Let's say you managed to get a ports tree and you want to compile and
install the archiving utility unzip. You should be able to
do something like this:
! % cd /usr/ports/archivers/unzip ! % su ! # make ! # make install ! # exit- Easy, huh? ! !
If you are interested in helping to expand the OpenBSD ports tree
you should first read porting.html.
--- 153,193 ----
Let's say you managed to get a ports tree and you want to compile and
install the archiving utility unzip. You should be able to
do something like this:
+
! % cd /usr/ports/archivers/unzip ! % su ! # make ! # make install ! # exit! Easy, huh ? Especially considering all that happened in the background: !
! In OpenBSD 2.7, a large proportion of the ports automatically build ! packages when installing. ! In OpenBSD current, almost all ports follow that standard. !
! As ports get built, the /usr/ports/distfiles directory gets filled with ! program sources, and /usr/ports/packages gets filled with binary packages. ! Users with low connectivity may refer to mirror-distfiles(7) for ! an efficient way to grab all distfiles at once. ! Note that the OpenBSD CD only include the ports tree and selected packages. ! If you wish to have the distfiles, you will have to get them through an ! independent way. +
If you are interested in helping to expand the OpenBSD ports tree you should first read porting.html. *************** *** 169,175 ****
! If you have trouble with ports please send e-mail to the OpenBSD ports mailing list, ports@openbsd.org. Corrections are always welcome, but in any case do please provide:
! If you have trouble with existing ports, or need information about creating new ports, ! please send e-mail to the OpenBSD ports mailing list, ports@openbsd.org. Corrections are always welcome, but in any case do please provide:
www@openbsd.org
!
www@openbsd.org
!