List of software package management systems

This is a list of notable software package management systems, categorized first by package format (binary, source code, hybrid) and then by operating system family.[1]

Binary packages

edit

The following package management systems distribute apps inbinarypackageform; i.e., all apps arecompiledand ready to be installed and use.

Unix-like

edit

Linux

edit
  • dpkg:Originally used byDebianand now byUbuntu.Uses the.deb formatand was the first to have a widely known dependency resolution tool,APT.Thencurses-based front-end for APT,aptitude,is also a popular package manager for Debian-based systems;
  • Entropy:Used by and created forSabayon Linux.It works with binary packages that are bzip2-compressed tar archives (file extension:.tbz2), that are created using Entropy itself, from tbz2 binaries produced byPortage:From ebuilds, a type of specialized shell script;
  • Flatpak:A containerized/sandboxed packaging format previously known as xdg-app;
  • GNU Guix:Used by the GNU System. It is based on theNix package managerwithGuileSchemeAPIs and specializes in providing exclusively free software;
  • Homebrew:a port of the MacOS package manager of the same name (see below), formerly referred to as 'Linuxbrew';
  • ipkg:Adpkg-inspired, very lightweight system targeted at storage-constrained Linux systems such as embedded devices and handheld computers. Used onHP's webOS;
  • netpkg:The package manager used byZenwalk.Compatible withSlackwarepackage management tools;
  • Nix package manager:Nix is a package manager for Linux and other Unix-like systems that makes package management reliable and reproducible. It provides atomic upgrades and rollbacks, side-by-side installation of multiple versions of a package, multi-user package management and easy setup of build environments;
  • OpenPKG:Cross-platform package management system based onRPM Package Manager;
  • opkg:Fork ofipkglightweight package management intended for use on embedded Linux devices;
  • Pacman:Used inArch Linux,FrugalwareandDeLi Linux.Its binary package format is a compressed tar archive (default file extension:.pkg.tar.zst) built using the makepkg utility (which comes bundled with pacman) and a specialized type of shell script called a PKGBUILD;
  • PETget:Used byPuppy Linux;
  • PISI:Stands for "Packages Installed Successfully as Intended". Pisi package manager is used by Pisi Linux.[2]Pardusused to use Pisi, but migrated to APT in 2013;[3]
  • pkgsrc:A cross-platform package manager, with binary packages provided for Enterprise Linux, macOS and SmartOS byJoyentand other vendors;
  • Portage:A package management system ran by theemergecommand, originally created for and used byGentoo Linux;
  • RPM Package Manager:Created byRed Hat.RPM is theLinux Standard Basepackaging format and the base of a number of additional tools, includingapt4rpm,Red Hat'sup2date,Mageia'surpmi,openSUSE'sZYpp(zypper),PLD Linux'spoldek,Fedora'sDNF,andYUM,which is used byRed Hat Enterprise Linux,andYellow Dog Linux;
  • slackpkg;
  • slapt-get:AnAPT-like package manager forSlackware;
  • Smart Package Manager:Used byCCux Linux;
  • Snap:Cross-distribution package manager, non-free on the server-side, originally developed forUbuntu;
  • Swaret;
  • xbps(X Binary Package System): Used byVoid Linux;
  • apk-tools:Used byAlpine Linux.Originally a collection of shell scripts, but has been since rewritten in C;

Android

edit

macOS (OS X)

edit
  • FreeBSD pkg– FreeBSD binary packages are built on top of source basedFreeBSD Portsand managed with pkg tool;
  • OpenBSD ports:The infrastructure behind the binary packages onOpenBSD;
  • pkgsrc:A cross-platform package manager, with regular binary packages provided forNetBSD,LinuxandmacOSby multiple vendors;
  • dpkg:Used as part ofDebian GNU/kFreeBSD;
  • OpenPKG:Cross-platform package management system based onrpm;
  • PC-BSD:Up to and including version 8.2[5]uses files with the.pbi(Push Button Installer) filename extension which, when double-clicked, bring up an installation wizard program. Each PBI is self-contained and uses de-duplicated private dependencies to avoid version conflicts. An autobuild system tracks theFreeBSD portscollection and generates new PBIs daily. PC-BSD also uses theFreeBSDpkg binary package system; new packages are built approximately every two weeks from both a stable and rolling release branch of theFreeBSDports tree.

Solaris, illumos

edit

Windows

edit

Superseded:

z/OS

edit

Source code-based

edit

The following package management systems distribute thesource codeof their apps. Either the user must know how to compile the packages, or they come with a script that automates the compilation process. For example, inGoboLinuxa recipe file contains information on how to download, unpack, compile and install a package using itsCompiletool. In both cases, the user must provide the computing power and time needed to compile the app, and is legally responsible for the consequences of compiling the package.

  • FreeBSD Portsis an original implementation of source based software management system commonly referred to asPorts collection.It gave way and inspired many others systems;
  • OpenBSD portsis a Perl based reimplementation of ports collection;

Linux

edit
  • ABSis used byArch Linuxto automate binary packages building from source or even other binary archives, with automatic download and dependency checking;
  • apt-buildis used by distributions which usedeb packages,allowing automatic compiling and installation of software in a deb source repository;
  • SorceryisSourcemage GNU/Linux'sbashbased package management program that automatically downloads software from their original site and compiles and installs it on the local machine;

macOS (OS X)

edit
  • Fink,forOS X,derives partially from dpkg/apt and partially from ports;
  • MacPorts,formerly called DarwinPorts, originated from theOpenDarwinproject;
  • Homebrew,with closeGitintegration;
  • pkgsrccan be used to install software directly from source-code, or to use the binary packages provided by several independent vendors.

Windows

edit

Hybrid systems

edit
  • Nix package manager:Package manager that manages software in apurely functionalway, featuring multi-user support, atomic upgrades and rollbacks. Allows multiple versions or variants of a software to be installed at the same time. It has support formacOSand is cross-distribution in itsLinuxsupport;
  • Portageandemergeare used byGentoo Linux,Funtoo Linux,andSabayon Linux.It is inspired by theBSD ports systemand uses text based "ebuilds" to automatically download, customize, build, and update packages from source code. It has automatic dependency checking and allows multiple versions of a software package to be installed into different "slots" on the same system. Portage also employs "use flags" to allow the user to fully customize a software build to suit the needs of their platform in an automated fashion. While source code distribution and customization is the preferred methodology, some larger packages that would take many hours to compile on a typical desktop computer are also offered as pre-compiled binaries in order to ease installation;
  • Upkg:Package management and build system based onMonoand XML specifications. Used bypaldoand previously by ExTiX Linux;
  • MacPorts(forOS X);
  • NetBSD'spkgsrcworks on severalUnix-likeoperating systems, with regular binary packages formacOSand Linux provided by multiple independent vendors;
  • Collective Knowledge Frameworkis a cross-platform package and workflow framework withJSONAPI that can download binary packages or build them from sources forLinux,Windows,MacOSandAndroidplatforms.[8]

Meta package managers

edit

The following unify package management for several or allLinuxand sometimesUnixvariants. These, too, are based on the concept of a recipe file.

  • AppImage(previously klik and PortableLinuxApps) aims to provide an easy way to get software packages for most major distributions without the dependency problems so common in many other package formats.
  • Autopackageuses.packagefiles.
  • PackageKitis a set of utilities and libraries for creating applications that can manage packages across multiple package managers using back-ends to call the correct program.

Game package managers

edit

Package management systems geared toward developing and distributing video games.

Proprietary software systems

edit

A wide variety of package management systems are in common use today byproprietary softwareoperating systems, handling the installation of both proprietary and free packages.

Application-level package managers

edit

Meta server application-level package manager

edit

See also

edit

References

edit
  1. ^Kolks, J.; Wright, T.; Raudenbush, B. (June 2009)."Effects of video game console and snack type on snack consumption during play".Appetite.52(3): 841.doi:10.1016/j.appet.2009.04.113.ISSN0195-6663.S2CID54404770.
  2. ^"Pisi GNU/Linux - Özgürlük Şimdi Başladı".pisilinux.org.Retrieved2020-10-27.
  3. ^"Pardus Tarihçe"(in Turkish).Retrieved2020-10-27.
  4. ^"Joyent Packages Documentation - Install On Mac OS X".Joyent.2016-06-04. Archived fromthe originalon 2018-10-06.Retrieved2018-05-04.
  5. ^pbiDIR
  6. ^"Joyent Packages Documentation - Install On Illumos".pkgsrc.joyent.Retrieved2017-02-26.
  7. ^"vcpkg: A C++ package manager for Windows, Linux and MacOS".
  8. ^"Portable and reproducible research workflows".GitHub.2017-03-27.Retrieved2017-03-27.