Zero Install

This article has multiple issues. Please help or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article relies too much on references to primary sources. Please improve this by adding secondary or tertiary sources. (December 2009) (Learn how and when to remove this template message) The topic of this article may not meet Wikipedia's notability guidelines for products and services. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources:  –  ·  ·  · scholar · JSTOR (July 2019) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

Zero Install

Zero Install ready to run a downloaded program
Developer(s)	Thomas Leonard
Stable release	2.17[1] / May 4, 2020; 20 months ago (2020-05-04)
Repository	github.com/0install/0install
Written in	OCaml
Operating system	Linux, Unix, macOS, Windows
Type	Package manager
License	LGPLv2.1
Website	0install.net

Zero Install is a means of distributing and packaging software for multiple operating systems (Unix-like including Linux and macOS, Windows).

Design[]

Rather than the normal method of downloading a software package, extracting it, and installing it before it can be used (with the accompanying use of destructive updates and privilege escalation), packages distributed using Zero Install need only be run. The first time software is accessed, it is downloaded from the Internet and cached; subsequently, software is accessed from the cache. Inside the cache, each application unpacks to its own directory, as in Application Directory systems.

The system is intended to be used alongside a distribution's native package manager.

Two advantages of Zero Install over more popular packaging systems are that it is cross-platform and no root password is needed to install software; packages can be installed in system locations writable by that user instead of requiring administrator access. Thus, package installation affects only the user installing it, which makes it possible for all users to be able to install and run new software.

Moreover, the EBox sandbox can be used on top of Zero Install to securely install software and to run them in a restricted environment.^[2]

Among the disadvantages of Zero Install is the fact that applications often need a rewrite for this packager, e.g. no absolute paths may be in use among other requirements. The quality of Zero Install repository content varies and may contain unmaintained software.

See also[]

• Application virtualization
• Portable application creators
• Java Web Start
• Advanced Packaging Tool
• Listaller
• Tar (computing) § Software distribution
• Autopackage
• AppImage
• ROX Desktop
• ClickOnce
• NixOS § Multi-user package management
• XAML Browser Applications (XBAP)
• Progressive Web Apps
• GNU Guix

References[]

External links[]

• Official website
• Thomas Leonard (2007-01-16). "Decentralised Installation Systems". OSNews.com.
• "pkgsrc and the concepts of package management 1997-2007 (part 2) - The Zero Install system". The NetBSD Project.
• Bruce Byfield (2007-02-15). "Zero Install: An executable critique of native package systems". linux.com.
• "Neue Zero Install-Implementation". pro-linux.de. 2005-06-24.
• "Zero Install: The Future of Linux on the Desktop?". Slashdot. 2004-04-03.