Nix (package manager)

Nix

Original author(s)	Eelco Dolstra
Initial release	June 15, 2003; 21 years ago (2003-06-15)
Stable release	2.22.1[1]  / 10 May 2024; 6 months ago (10 May 2024)
Repository	github.com/NixOS/nix
Written in	C++,[2] Perl,[2] shell script,[2] Nix,[2] make,[2] Autoconf,[2] Rust,[2] C,[2] XML[2]
Platform	Linux, Darwin, FreeBSD,[3] OpenBSD[4]
Type	purely functional package manager, free and open-source software, implementation of a programming language, reference implementation, interpreter
License	GNU Lesser General Public License, version 2.1[5]
Website	nixos.org

Nix is a cross-platform package manager for Unix-like systems, and a tool to instantiate and manage those systems, invented in 2003^[6] by Eelco Dolstra.

The Nix package manager employs a model in which software packages are each installed into unique directories with immutable contents. These directory names correspond to cryptographic hashes that take into account all dependencies of a package, including other packages managed by Nix. As a result, Nix package names are content-identifying since packages with the same name will have had the same inputs and the same build platform, and therefore the same build result.^[7]

Package recipes for Nix are written in the purpose-built "Nix language", a declarative, purely functional, lazily evaluated, dynamically typed programming language.^[8] Distinguishing features of the Nix language are strings with "context", string interpolation, first-class file system paths, and "indented strings", which in combination allow concisely expressing dependencies between file system data when specifying the contents of new files.

Dependencies between files, as declared in the Nix language, are automatically tracked and persisted in the "Nix store".^[9] New files in the Nix store are created through "derivations". A derivation is a persistent data structure that specifies an executable, arguments and environment variables for its invocation (see execve), and other files to be read from the Nix store. The executable is then run in a sandbox that prohibits access to anything but the explicitly specified input files and only allows writing to the designated output path. Nix preserves dependency information in output files by scanning for the distinctive hashes used for package directory names.^[7]

Automatic reference tracking ensures integrity of packages, even when they are transferred across machines. It also enables garbage collection of unused packages when no other package depends on them. At the cost of greater storage requirements, all upgrades in Nix are guaranteed to be both atomic and capable of efficient rollback. Unique directory names allow installing many packages with differing versions of shared libraries, and is claimed to eliminate so-called dependency hell.^[10] This also lets multiple users safely install software on the same system without administrator privileges. As a result, the Nix package management and deployment model advertises more reliable, reproducible, and portable packages.^[7][11]

Nix has full support for Linux, macOS, and WSL, and can safely be installed side-by-side with another package manager.

Nixpkgs is the package repository built upon the Nix package manager. According to Repology, as of July 2024 it contains more than 110,000 packages^[12] and has a higher number of up-to-date packages than any other package repository.^[13] Operating systems supported by Nixpkgs are primarily Linux and Darwin, with some support for Windows and BSD variants. Supported CPU architectures include 64-bit x86 and ARM. Packages for these architectures are built regularly, using a continuous integration service called Hydra,^[14] and the results of these builds are uploaded to a public binary cache.^[15] When Nix installs a package, it checks this cache and downloads the binary package to avoid building it locally.

Nixpkgs is developed in a single Git repository on GitHub.^[16] Beside packages, it also contains the source code for NixOS.

NixOS^[17] is a Linux distribution that uses Nix for managing the entire system configuration, including the Linux kernel.^[18]

Nix is used for software packaging and distribution in CERN's LHCb experiment.^[19] Nix underlies the distributed software development platforms Replit^[20] and Google IDX.^[21]

In 2021, a reimplementation by the name Tvix was announced,^[22] with the goals of modularity, full compatibility with Nixpkgs, and improved evaluator performance. As of 2024, Tvix has an evaluator^[23] and a store implementation,^[24] though the authors do not consider the project yet stable or ready for use in production.^{[25][non-primary source needed]} Tvix is written primarily in Rust.^[26]

In 2024, a team of volunteers released the first version of Lix,^{[27][non-primary source needed]} a fork of Nix focused on correctness and compatibility that uses the Meson build automation system. The project intends to gradually rewrite parts of the code in Rust.^[27]

• GNU Guix: another declarative package manager, and early clone of Nix, using GNU Guile for configuration and customization
• Maak: a build automation utility similar to make, and early precursor to Nix
• Runbook automation

Wikidata has the property:

• nixpkgs ID (P12433) (see uses)

• Official website
• Nix on GitHub
• Discussion among developers on the Debian mailing list (2008)