add site
services
publishers
database
health videos
toolbar
stats
live show
health store
more stuff
JOIN/LOGIN
| advertise add site services publishers database health videos
| | about toolbar stats live show health store more stuff JOIN/LOGIN |
and Day trips from Florida... funandsun.com | Port Isabel Dental Associates ~ Dental Care in Port Isabel, TX ~ Texas... graysonsellers.com |
The FreeBSD Ports collection is a package management system which provides an easy and consistent way of installing software packages on the FreeBSD operating system. As of August 2009 there are over 20,500 ports [1] available in the collection. It has also been adopted by NetBSD as the basis for their pkgsrc system.
[edit] Installing from sourceThe ports system uses Makefiles laid out in a directory hierarchy so software can be built, installed and uninstalled with the make command. When installing an application, very little (if any) user intervention is required after issuing a beginning command such as make install or make install clean in the ports directory of the desired application. In most cases the software is automatically downloaded from the Internet, patched and configured if necessary, then compiled, installed and registered in the package database. If the new port has needed dependencies on other applications or libraries, these are installed beforehand automatically. Most ports are already configured with default options which have been deemed generally appropriate for most users. However, these configuration options can sometimes be changed with the make config command before installation or through an ncurses interface allowing the user to graphically select the desired options. Historically, each port (or software package) has been maintained by an individual person called a port maintainer who is responsible for staying current with the latest software developments and providing general support. Today, many ports are maintained by special task forces or sub-projects, each with a dedicated mailing list, e.g. kde@FreeBSD.org, java@FreeBSD.org, etc., while unmaintained ports are assigned to ports@FreeBSD.org. In general, anyone is welcome to become a port maintainer by contributing their favorite piece of software to the collection. One may also choose to adopt and maintain an existing port if it currently has no maintainer. Information on how to create and maintain ports can be found in the Porter's Handbook. [edit] PackagesPrecompiled (binary) ports are called packages, which are available for download. A user can easily and automatically install a package by passing the package name to the pkg_add -r command. This downloads the appropriate package for the user's release version of FreeBSD, then installs the application along with any software dependencies it may have. By default, this command downloads packages from the main FreeBSD distribution site. FreeBSD maintains a build farm called the pointyhat cluster in which all packages for all architectures and major releases are built. The build logs and known errors for all ports built into packages through the pointyhat cluster are available in a database. These precompiled packages are separated into categories by the architectures for which they are available. Packages are further separated into several "release" directories, one for each current production release built from the ports collection and shipped with the release. These production release directories are never updated. There are also stable and current directories for several major release branches. These are updated more or less weekly. In most cases a package created for an older version of FreeBSD can be installed and used on a newer system without difficulty since binary backward compatibility across major releases is enabled by default. [edit] HistoryJordan Hubbard committed his port make macros to the FreeBSD CVS repository on August 21, 1994. His package install suite had been committed a year earlier (August 26, 1993). The core ports framework was at first maintained by Hubbard along with Satoshi Asami for several years. The Ports Management Team was later formed to handle this task. [edit] External links
[edit] References
| |||||||||||||
| ↑ top of page ↑ | about thumbshots |
