Sheng chuan trading options35 comments
Opcje binarne bez depozytu 2016
As of April , there are over 31, ports  available in the collection. It has also been adopted by NetBSD as the basis of its pkgsrc system. The ports collection uses Makefiles arranged in a directory hierarchy so that 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 called knobs can sometimes be changed before installation using the make config command, which brings up a text-based interface that allows the user to select the desired options.
Historically, each port or software package has been maintained by an individual port maintainer who is responsible for ensuring the currency of the port and providing general support. Today, many ports are maintained by special task forces or sub-projects, each with a dedicated mailing list e. In general, anyone may become a port maintainer by contributing their favorite software to the collection.
One may also choose to maintain an existing port with no active maintainer. Precompiled binary ports are called packages. A package can be created from the corresponding port with the make package command; prebuilt packages are also available for download from FreeBSD-hosted package repositories. A user can install a package by passing the package name to the pkg install command. This downloads the appropriate package for the installed FreeBSD release version , then installs the application, including any software dependencies it may have.
FreeBSD maintains a build farm called the pointyhat cluster in which all packages for all supported 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. A packaging system called pkg has replaced the package management system in FreeBSD The Ports Management Team was later formed to handle this task. From Wikipedia, the free encyclopedia.