pkgsrc
| NetBSD Packages Collection | |
|---|---|
| Basic data
|
|
| Maintainer | Alistair Crooks, Hubert Feyrer, Johnny C. Lam |
| Publishing year | 1997 |
| Current version | 2019Q4 (01/06/2020) |
| operating system | AIX , BSD / OS , Darwin ( macOS ), DragonFly BSD , FreeBSD , HP-UX , Interix , IRIX , Linux , NetBSD , OpenBSD , OSF / 1 , Solaris , QNX , MirBSD, Minix |
| programming language | C. |
| category | Package management |
| License | BSD license |
| pkgsrc.org | |
pkgsrc ( package source ) is a package manager for UNIX-like operating systems. It is the standard package manager for NetBSD , SmartOS , and Minix .
In contrast to many other package managers, it runs on almost all UNIX-like operating systems and is not restricted to a specific directory - e.g. B. /usr- and can also be installed by users who do not have system administrator rights.
The preferred installation method for pkgsrc is to compile from the source code of the packages, but there are also ready-made binary packages for some operating systems, especially NetBSD .
pkgsrc is published open source under BSD license .
use
Binary packages
pkgsrc provides a few commands with which binary packages can be installed ( pkg_add), updated and removed from the system ( pkg_delete). The binary packages for NetBSD are available on the FTP server of the NetBSD project.
Using binary packages has the disadvantage that not all programs from the pkgsrc directory (see web links ) are available. In particular, there are no packets that cannot be redistributed. Another disadvantage is that the binary packages lose their relevance over time.
At the end of each quarter, pkgsrc creates a "stable" branch. The packages in this branch are only updated when security vulnerabilities are fixed. Binary packets are also generated from these branches for some of the platforms supported by NetBSD. Updates are more frequent in the “development branch”, but experimental innovations are regularly incorporated here, so that it is possible that some packages cannot be installed.
From the sources
If there are no binary packages for a platform, the only option is to build the packages yourself from the sources. In addition, there are additional options for many packages that must be specified at the time of compilation. Another reason to install pkgsrc from the sources is that a large number of packages can also be installed by "normal" users, so they do not require system administrator rights. Binary packages are generally not provided for such configurations, since the directory in which the packages are installed is often selected individually. In the Wip branch (Work-In-Progress), non-official packages are maintained by developers and can be used together with the regular ones, similar to the port tree .
Release cycle
The pkgsrc developers publish a new version every three months. This is named after the current year and quarter - e.g. B. pkgsrc-2015Q2. In a two-week “freeze period” before the release, the development focus is on stability.
Security updates are backported to the latest version.
Individual evidence
- ^ The pkgsrc Open Source Project on Open Hub: Languages Page . In: Open Hub . (accessed on July 18, 2018).
- ↑ Pkgsrc-Wip