Nix package manager
1.11.15 / September 15, 2017
|Written in||C, C++, Perl|
Nix is a package manager for computer systems. Like RPM, APT and many other package managers, it is able to control the installation of packages, or named and versioned groups of files, such as software applications or their associated configuration data.
Nix packages are configured using a lazy, purely functional language specially designed for this purpose; shell scripts or any other external program (such as Make) may be used to build packages from source code. The purely functional nature of the system enables very precise dependency tracking; for example, a binary package has a dependency on the corresponding source package, on the compiler, and on other packages that the build requires. Cryptographic hashes determine the exact build and run-time dependencies of every package, and each source or binary package is represented by such a hash. As a result, binary package repositories are a transparent optimization of the basic operation of the package manager (similar to a "cache" of packages indexed by a cryptographic hash).
Dependencies are resolved by a system functionally equivalent to hard linking, in that versions of software being depended on by a package are not removed until no package is dependent on them. This can lead to greater storage needs, but makes all upgrades safe (guaranteed not to break existing applications) and atomic. It also permits multiple versions of any package, including parametrised packages such as a program with and without a certain feature, to coexist with no interference.
Nix depends upon having its own directory structure for installing the packages. All packages are installed in sub-directories of the nix directory. In naming the folders, different versions of a package are identified by prepending the hash to the package name.
Nix can be used, with some caveats, as a package manager on top of an existing operating system, such as a GNU/Linux distribution. It may also be used to maintain any kind of file configurations, such as server setups, in addition to software packages in the strict sense.
- Maak - A build automation utility similar to make, designed to build complex software systems.
- Scripting language
- Package (package management system)
- GNU Guix - Another declarative package manager for GNU/Linux distributions, built on Nix but which uses the more ubiquitous GNU Guile for configuration and customization, instead of the domain-specific language of Nix.
- Batch processing
- Office automation
- Runbook Automation - One of the potential applications for package managers
- Software engineering
- Dolstra, Eelco (2017-09-15). "Release 1.11.15" (Mailing list). Retrieved 2017-09-15.
- Prins, P., Suresh, J. and Dolstra, E., "Nix fixes dependency hell on all Linux distributions," linux.com, December 22, 2008
- Dolstra, E., de Jonge, M. and Visser, E. "Nix: A Safe and Policy-Free System for Software Deployment." In Damon, L. (Ed.), 18th Large Installation System Administration Conference (LISA '04), pages 79–92, Atlanta, Georgia, USA. USENIX, November 2004.
- Dolstra, E. The Purely Functional Software Deployment Model. PhD thesis, Faculty of Science, Utrecht, The Netherlands. January 2006. ISBN 90-393-4130-3.
- Dolstra, E. and Löh, A. "NixOS: A Purely Functional Linux Distribution." In ICFP 2008: 13th ACM SIGPLAN International Conference on Functional Programming, pages 367–378, Victoria, British Columbia, Canada. September 2008.
- Official website
- Comparison of Zero Install and systems such as Nix
- Debian developer criticism (2008)
- Introduction: Purely Functional Configuration Management with Nix and NixOS