Zero Install
 Zero Install ready to run a downloaded program | |
| Developer(s) | Thomas Leonard |
|---|---|
| Stable release | 2.17[1]
/ May 4, 2020 |
| Written in | OCaml |
| Engine | |
| Operating system | Linux, Unix, macOS, Windows |
| Type | Package manager |
| License | LGPLv2.1 |
| Website | 0install |
Search Zero Install on Amazon.
Zero Install is a means of distributing and packaging software for multiple operating systems (Unix-like including Linux and macOS, Windows).
Software[edit]
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 to be run. The first time software is accessed, it is downloaded from the Internet and cached; subsequently, the software is accessed from the cache. Inside the cache, each application is unpacked into its own directory, similarly to what is done with application directories.
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[edit]
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 that 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[edit]
- 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[edit]
- ↑ "Releases · 0install/0install". GitHub.
- ↑ "Ebox - Zero Install Docs".
- ↑ "Install the User Client on Windows". PaperCut. Retrieved 2022-09-14.
- ↑ "Zero-Installs". yarnpkg.com. Retrieved 2022-09-14.
External links[edit]
- 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.
| dpkg | |
|---|---|
| RPM | |
| Embedded systems | |
| Distribution-agnostic | |
| Others (binary) | |
| Others (source) | |
| Front-ends | |
| Related topics | |
This article "Zero Install" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Zero Install. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
