List of software package management systems

From Wikipedia, the free encyclopedia
  (Redirected from Meta package managers)
Jump to: navigation, search

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

Binary packages[edit]

The following package management systems distribute apps in binary package form; i.e., all apps are compiled and ready to be installed and use.

Unix-like[edit]

Linux[edit]

  • DIRECT: Commercial cross-platform deployment solution for user-installed applications, developed by Solid State Networks. Used for install, update, repair, uninstall of PC online games. Works on Windows, macOS and Linux.
  • dpkg: Originally used by Debian and now by Ubuntu. Uses the .deb format and was the first to have a widely known dependency resolution tool, APT. The ncurses-based front-end for APT, aptitude, is also a popular package manager for Debian-based systems.
  • Entropy: used by and created for Sabayon 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 by Portage 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 the Nix package manager with Guile Scheme APIs and specializes in providing exclusively free software.
  • ipkg: A dpkg-inspired, very lightweight system targeted at storage-constrained Linux systems such as embedded devices and handheld computers. Used on HP's webOS.
  • netpkg
  • Nix package manager: Package manager that manages software in a purely functional way, featuring multi-user support, atomic upgrades and rollbacks. Allows multiple versions or variants of a software to be installed at the same time. It also has support for macOS and is cross-distribution in its Linux support.
  • OpenPKG: Cross-platform package management system based on RPM Package Manager
  • opkg: Fork of ipkg
  • pacman: Used in Arch Linux, Frugalware and DeLi Linux. Its binary package format is a xz-compressed tar archive (file extension: .pkg.tar.xz) built using the makepkg utility (which comes bundled with pacman) and a specialized type of shell script called a PKGBUILD.
  • PETget: used by Puppy Linux
  • PISI: Used by Pardus
  • RPM Package Manager: Created by Red Hat. RPM is the Linux Standard Base packaging format and the base of a number of additional tools, including apt4rpm, Red Hat's up2date, Mageia's urpmi, openSUSE's ZYpp (zypper), PLD Linux's poldek, Fedora's DNF, and YUM, which is used by Red Hat Enterprise Linux, and Yellow Dog Linux.
  • slackpkg
  • slapt-get, which is used by Slackware and works with a binary package format that is essentially a xz-compressed tar archive with the file extension .txz.
  • Smart Package Manager: Used by CCux Linux
  • Snappy: cross-distribution package manager, originally developed for Ubuntu.
  • Steam: A cross-platform video game distribution, licensing and social gameplay platform, developed and maintained by Valve. Used to shop for, download, install, update, uninstall and back up video games. Works on Windows NT, OS X and Linux.
  • swaret
  • Zero Install (0install): Cross-platform packaging and distributions software. It is available for Arch Linux, Debian, Knoppix, Mint, Ubuntu, Fedora, Gentoo, OpenSUSE, Red Hat and Slackware.

macOS (OS X)[edit]

  • Mac App Store: Official digital distribution platform for OS X apps. Part of OS X 10.7 and available as an update for OS X 10.6.
  • Homebrew: Package manager for OS X, based on Git
  • Fink: A port of dpkg, it is one of the earliest package managers for OS X.
  • MacPorts: Formerly known as DarwinPorts, based on FreeBSD Ports (as is OS X itself)
  • Joyent: Provides a repository of 10,000+ binary packages for OS X based on pkgsrc[1]
  • Nix package manager: 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
  • Zero Install (0install): Cross-platform packaging and distributions software. Uses GnuPG and GTK+ on OS X.
  • DIRECT: Commercial cross-platform deployment solution for user-installed applications, developed by Solid State Networks. Used for install, update, repair, uninstall of PC online games. Works on Windows, macOS and Linux.
  • Steam: A cross-platform video game distribution, licensing and social gameplay platform, developed and maintained by Valve. Used to shop for, download, install, update, uninstall and back up video games. Works on Windows NT, OS X and Linux.

BSD[edit]

  • dpkg: Used as part of Debian GNU/kFreeBSD
  • OpenPKG: Cross-platform package management system based on rpm
  • PC-BSD 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 the FreeBSD ports collection and generates new PBIs daily. PC-BSD also uses the FreeBSD pkg binary package system; new packages are built approximately every two weeks from both a stable and rolling release branch of the FreeBSD ports tree.
  • PKGNG: now standard; available in FreeBSD and PC-BSD since 9.1,[2] with support for binary packages

Solaris,illumos[edit]

Mobile[edit]

Android[edit]

iOS[edit]

Windows[edit]

  • Windows Store: Official app store for Metro-style apps on Windows NT and Windows Phone. As of Windows 10, it distributes video games, films and music as well.
  • Windows Phone Store: Former official app store for Windows Phone. Now superseded by Windows Store.
  • Xbox Live: A cross-platform video game distribution platform by Microsoft. Works on Windows NT, Windows Phone and Xbox. Initially called Games for Windows – Live on Windows 7 and earlier. On Windows 10, the distribution function is taken over by Windows Store.
  • Cygwin: Free and open-source software repository for Windows NT. Provides many Linux tools and an installation tool with package manager.
  • Ninite: Proprietary package manager for Windows NT
  • NuGet: A Microsoft-official free and open-source package manager for Windows, available as a plugin for Visual Studio, and extendable from the command-line.
  • Chocolatey: Open-source decentralized package manager for Windows in the spirit of Yum and apt-get. Usability wrapper for NuGet
  • pacman: MSYS2-ported Windows version of the Arch Linux package manager.
  • wpkg: Open-source package manager that handles Debian packages on Windows. Started as a clone of dpkg, and has many apt-get like features too.
  • Zero Install (0install): Cross-platform packaging and distributions software. Uses .NET Framework on Windows NT.
  • DIRECT: Commercial cross-platform deployment solution for user-installed applications, developed by Solid State Networks. Used for install, update, repair, uninstall of PC online games. Works on Windows, macOS and Linux.
  • Steam: A cross-platform video game distribution, licensing and social gameplay platform, developed and maintained by Valve. Used to shop for, download, install, update, uninstall and back up video games. Works on Windows NT, OS X and Linux.
  • Uplay: A cross-platform video game distribution, licensing and social gameplay platform, developed and maintained by Ubisoft. Used to shop for, download, install and update video games. Works on Windows NT and Windows Phone, as well as PlayStation 3, PlayStation 4, Xbox 360, Xbox One, Wii U, iOS and Android.

z/OS[edit]

Source code-based[edit]

The following package management systems distribute the source code of 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, in GoboLinux a recipe file contains information on how to download, unpack, compile and install a package using its Compile tool. 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.

  • apt-build is used by distributions which use deb packages, allowing automatic compiling and installation of software in a deb source repository.
  • Sorcery is Sourcemage GNU/Linux's bash based package management program that automatically downloads software from their original site and compiles and installs it on the local machine.
  • ABS is used by Arch Linux to automate binary packages building from source or even other binary archives, with automatic download and dependency checking.

macOS (OS X)[edit]

  • fink, for OS X, derives partially from dpkg/apt and partially from ports.
  • MacPorts, formerly called DarwinPorts, originated from the OpenDarwin project.
  • Homebrew, with close Git integration.

Hybrid systems[edit]

  • Portage and emerge are used by Gentoo Linux, Funtoo Linux, and Sabayon Linux. It is inspired by the BSD ports system and 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 on Mono and XML specifications. Used by paldo and previously by ExTiX Linux.
  • MacPorts (for OS X)
  • NetBSD's pkgsrc works on several Unix-like operating systems.
  • Collective Knowledge Framework is a cross-platform package and workflow framework with JSON API that can download binary packages or build them from sources for Linux, Windows, MacOS and Android platforms[6]

Meta package managers[edit]

The following unify package management for several or all Linux and sometimes Unix variants. 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.
  • Autopackage uses .package files.
  • Zero Install installs each package into its own directory and uses environment variables to let each program find its libraries. Package and dependency information is downloaded directly from the software authors' pages in an XML format, similar to an RSS feed.
  • PackageKit is 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.

Proprietary software systems[edit]

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

Application-level Dependency managers[edit]

See also[edit]

References[edit]

  1. ^ "Joyent Packages Documentation: Installing on OS X". Joyent. 2014-07-10. Retrieved 2014-10-18. 
  2. ^ "PKGNG – The future of packages on FreeBSD and PC-BSD". www.ixsystems.com. iXsystems. 30 August 2013. 
  3. ^ "Joyent Packages Documentation - Install On Illumos". pkgsrc.joyent.com. Retrieved 2017-02-26. 
  4. ^ "F-Droid, the Android app store for freedom beards.". 2011-08-24. Retrieved 2014-10-18. 
  5. ^ Alexis Kauffmann (2011-10-10). "Le projet Replicant ou Android totalement libre présenté par PaulK" (in French). Retrieved 2014-10-18. 
  6. ^ "Portable and reproducible research workflows". 2017-03-27. Retrieved 2017-03-27. 
  7. ^ http://bower.io
  8. ^ https://crates.io/
  9. ^ https://github.com/Carthage/Carthage
  10. ^ "noteflakes/lyp". GitHub. Retrieved 2016-12-21. 
  11. ^ https://opam.ocaml.org
  12. ^ https://yarnpkg.com/