This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article relies excessively on references to primary sources. Please improve this by adding secondary or tertiary sources. Find sources: "Zero Install" – news · newspapers · books · scholar · JSTOR (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: "Zero Install" – news · newspapers · books · scholar · JSTOR (July 2019) (Learn how and when to remove this template message) (Learn how and when to remove this template message)
Zero Install
Developer(s)Thomas Leonard
Stable release
2.17[1] / May 4, 2020; 2 years ago (2020-05-04)
Repository
Written inOCaml
Operating systemLinux, Unix, macOS, Windows
TypePackage manager
LicenseLGPLv2.1
Website0install.net

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

Software

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 only need 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.

Other uses of the term

Other uses of the term "Zero Install" exist which are unrelated to a specific software project.

PaperCut software describes a "zero install strategy" for Windows networks, which involves configuring multiple terminals via methods such as a group policy, to run the client executable directly off a single share. This enables automatic updates for workstations in line with the server and avoids multiple, separate installation processes.[3]

The Yarn package manager describes a zero-install as a philosophy which seeks to limit failures by limiting the usage of Yarn commands and therefore limiting the number of opportunities for things to go wrong.[4]

See also

References

  1. ^ "Releases · 0install/0install". GitHub.
  2. ^ "Ebox - Zero Install Docs".
  3. ^ "Install the User Client on Windows". PaperCut. Retrieved 2022-09-14.
  4. ^ "Zero-Installs". yarnpkg.com. Retrieved 2022-09-14.