If you are building Guix from source, please see the manual for build instructions and requirements, either by running:

info -f doc/guix.info "Requirements"

or by checking the web copy of the manual.

See the manual for the installation instructions, either by running

info -f doc/guix.info "Installation"

or by checking the web copy of the manual.

For information on building Guix from a Git checkout, please see the relevant section in the manual, either by running

info -f doc/guix.info "Building from Git"

or by checking the web_copy of the manual.

Guix does the high-level preparation of a derivation. A derivation is the promise of a build; it is stored as a text file under /gnu/store/xxx.drv. The (guix derivations) module provides the `derivation' primitive, as well as higher-level wrappers such as `build-expression->derivation'.

Guix does remote procedure calls (RPCs) to the build daemon (the guix-daemon command), which in turn performs builds and accesses to the store on its behalf. The RPCs are implemented in the (guix store) module.

GNU Guix is hosted at https://savannah.gnu.org/projects/guix/.

Please email <help-guix@gnu.org> for questions and <bug-guix@gnu.org> for bug reports; email <gnu-system-discuss@gnu.org> for general issues regarding the GNU system.

Join #guix on irc.libera.chat.

GNU Guix is based on the Nix package manager. It implements the same package deployment paradigm, and in fact it reuses some of its code. Yet, different engineering decisions were made for Guix, as described below.

Nix is really two things: a package build tool, implemented by a library and daemon, and a special-purpose programming language. GNU Guix relies on the former, but uses Scheme as a replacement for the latter.

Using Scheme instead of a specific language allows us to get all the features and tooling that come with Guile (compiler, debugger, REPL, Unicode, libraries, etc.) And it means that we have a general-purpose language, on top of which we can have embedded domain-specific languages (EDSLs), such as the one used to define packages. This broadens what can be done in package recipes themselves, and what can be done around them.

Technically, Guix makes remote procedure calls to the ‘nix-worker’ daemon to perform operations on the store. At the lowest level, Nix "derivations" represent promises of a build, stored in ‘.drv’ files in the store. Guix produces such derivations, which are then interpreted by the daemon to perform the build. Thus, Guix derivations can use derivations produced by Nix (and vice versa).

With Nix and the Nixpkgs distribution, package composition happens at the Nix language level, but builders are usually written in Bash. Conversely, Guix encourages the use of Scheme for both package composition and builders. Likewise, the core functionality of Nix is written in C++ and Perl; Guix relies on some of the original C++ code, but exposes all the API as Scheme.

• Nix, Nixpkgs, and NixOS, functional package manager and associated software distribution, are the inspiration of Guix
• GNU Stow builds around the idea of one directory per prefix, and a symlink tree to create user environments
• STORE shares the same idea
• GNOME's OSTree allows bootable system images to be built from a specified set of packages
• The GNU Source Release Collection (GSRC) is a user-land software distribution; unlike Guix, it relies on core tools available on the host system

GNU Guix is made available under the GNU GPL version 3 or later license, and authors retain their copyright. For copyright notices, we adhere to the guidance documented in (info "(maintain) Copyright Notices"), and explicitly allow ranges instead of individual years. Here's an example of the preferred style used for copyright notices in source file headers:

Meaning there were copyright-able changes made for the years 2019, 2020, 2021, 2022, 2023 and 2025.