Differing from traditional package managers, Guix (like Nix) utilizes a purely functional deployment model where software is installed into unique directories generated through cryptographic hashes. All dependencies for each software are included within each hash.[4][5] This solves the problem of dependency hell,[6] allows multiple versions of the same software to coexist and makes packages portable and reproducible. Performing scientific computations in a Guix setup has been proposed as a promising response to the replication crisis.[7][8]
Guix packages are defined through functional Guile Scheme APIs specifically designed for package management. Dependencies are tracked directly in this language through special values called "derivations" which are evaluated by the Guix daemon lazily. Guix keeps track of these references automatically so that installed packages can be garbage collected when no other package depends on them. At the cost of greater storage requirements, all upgrades in Guix are guaranteed to be both atomic and can be rolled back. The roll-back feature of Guix is inherited from the design of Nix and is not found in any of the native package managers of popular Linux distributions such as Debian and its derivatives, Arch Linux and its derivatives, or in other major distributions such as Fedora, CentOS or openSUSE. The Guix package manager can however be used in such distributions and is available for Debian and Parabola.[13][14] This also enables multiple users to safely install software on the same system without administrator privileges.
Compared to traditional package managers, Guix package stores can grow considerably bigger and therefore require more bandwidth; although compared to container solutions (like Docker) that are also commonly employed to solve dependency hell, Guix is leaner and conforms to practices like Don't repeat yourself and Single source of truth. If the user chooses to build everything from source even larger storage space and bandwidth is required.
The store
Inherited from the design of Nix, most of the content of the package manager is kept in a directory /gnu/store where only the Guix daemon has write-access. This is achieved via specialised bind mounts, where the Store as a file system is mounted read only, prohibiting interference even from the root user, while the Guix daemon remounts the Store as read/writable in its own private namespace. Guix talks with this daemon to build things or fetch substitutes which are all kept in the store. Users are discouraged from ever manually touching the store by re-mounting it as writable since this defeats the whole purpose of the store.
Garbage collection
Guix - like Nix - has built-in garbage collection facilities to help prune dead store items and keep the live ones.[15]
Package definitions
This is an example of a package definition for the hello-package:
(define-publichello(package(name"hello")(version"2.10")(source(origin(methodurl-fetch)(uri(string-append"mirror://gnu/hello/hello-"version".tar.gz"))(sha256(base32"0ssi1wpaf7plaswqqjwigppsg5fyh99vdlb9kzl7c9lng89ndq1i"))))(build-systemgnu-build-system)(synopsis"Hello, GNU world: An example GNU package")(description"GNU Hello prints the message \"Hello, world!\" and then exits. It serves as an example of standard GNU coding practices. As such, it supports command-line arguments, multiple languages, and so on.")(home-page"https://www.gnu.org/software/hello/")(licensegpl3+)))
It is written using Guile. The package recipes can easily be inspected (running e.g. guix edit hello) and changed in Guix, making the system transparent and very easy to modify.
Transactional upgrades
Inherited from the design of Nix, all manipulation of store items is independent of each other, and the directories of the store begin with a base32-encoded hash of the source code of the derivation along with its inputs.
Profiles
Guix package uses profiles generations, which are a collection of symlinks to specific store items together comprising what the user has installed into the profile. Every time a package is installed or removed, a new generation will be built.
E.g. the profile of a user who only installed GNU Hello contains links to the store item which holds the version of hello installed with the currently used guix.
E.g. on version c087a90e06d7b9451f802323e24deb1862a21e0f of guix, this corresponds to the following item: /gnu/store/md2plii4g5sk66wg9cgwc964l3xwhrm9-hello-2.10 (built from the recipe above).
In addition to symlinks, each profile guix builds also contains a union of all the info-manuals, man-pages, icons, fonts, etc. so that the user can browse documentation and have access to all the icons and fonts installed.
The default symlinks to profile generations are stored under /var/guix in the filesystem.
Multiple user profiles
The user can create any number of profiles by invoking guix package -p PROFILE-NAME COMMAND. A new directory with the profile-name as well as profile-generation-symlinks will then be created in the current directory.
Roll-back
Guix package enables instantaneous roll-back to a previous profile generation via changing the symlink to an earlier profile generation.[16] Profiles are also stored in the store e.g. this item is a profile containing hello above: /gnu/store/b4wipjlsapvnijmbawl7sh76087vpl4n-profile (built and activated when running guix install hello).
Shell environment
Guix shell enables the user to easily enter an environment where all the necessary packages for development of software are present without clogging up the users default profile with dependencies for multiple projects.[17]
E.g. running guix shell --development hello enters a throw-away environment where everything needed to compile hello on guix is present (gcc, guile, etc.).
Without the --development flag, only the package hello would be installed and not its build-dependencies. This supplants the guix environment command, which installs the dependencies of a package by default, as it was considered more intuitive for the command to install the specified packages by default and only install development dependencies with a flag.[18]
Persistent development environment
If you want a persistent gc-rooted environment that is not garbage collected on the next run of guix gc you can create a root:
E.g. running guix shell --root=hello-root --development hello enters an environment where everything needed to compile guix is present (gcc, guile, etc.) and registered as a root in the current directory (by symlinking to the items in the store).
Pack
Guix pack enables the user to bundle together store items and output them as a docker binary image, a relocatable tarball or a squashfs binary.[19]
Graph
Guix graph enables the user to view different graphs of the packages and their dependencies.[20]
GNU Guix System uses Guix as its package manager and configuration system, similar to how NixOS uses Nix.
History
The GNU Project announced in November 2012 the first release of GNU Guix, a functional package manager based on Nix that provides, among other things, GuileSchemeAPIs.[21] The project was started in June 2012 by Ludovic Courtès, one of the GNU Guile hackers.[22] On August 20, 2015, it was announced that Guix had been ported to GNU Hurd.[23]
Releases
The project has no fixed release schedule and has until now released approximately every 6 months.
/ 19 December 2022
