projects/guix·blob version-1.2.0 · refs

110 lines · 4.8 KiB

-*- mode: org -*-

[[https://www.gnu.org/software/guix/][GNU Guix]] (IPA: /ɡiːks/) is a purely functional package manager, and
associated free software distribution, for the [[https://www.gnu.org/gnu/gnu.html][GNU system]].  In addition
to standard package management features, Guix supports transactional
upgrades and roll-backs, unprivileged package management, per-user
profiles, and garbage collection.

It provides [[https://www.gnu.org/software/guile/][Guile]] Scheme APIs, including a high-level embedded
domain-specific languages (EDSLs) to describe how packages are to be
built and composed.

GNU Guix can be used on top of an already-installed GNU/Linux distribution, or
it can be used standalone (we call that “Guix System”).

Guix is based on the [[https://nixos.org/nix/][Nix]] package manager.


* Requirements

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 [[https://guix.gnu.org/manual/en/html_node/Requirements.html][web copy of the manual]].

* Installation

See the manual for the installation instructions, either by running

  info -f doc/guix.info "Installation"

or by checking the [[https://guix.gnu.org/manual/en/html_node/Installation.html][web copy of the manual]].

* Building from Git

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 [[https://guix.gnu.org/manual/en/html_node/Building-from-Git.html][web_copy of the manual]].

* How It Works

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.

* Contact

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

Please email <[email protected]> for questions and <[email protected]> for bug
reports; email <[email protected]> for general issues regarding the
GNU system.

Join #guix on irc.freenode.net.

* Guix & Nix

GNU Guix is based on [[https://nixos.org/nix/][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 [[https://nixos.org/nixpkgs][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.

* Related software

  - [[https://nixos.org][Nix, Nixpkgs, and NixOS]], functional package manager and associated
    software distribution, are the inspiration of Guix
  - [[https://www.gnu.org/software/stow/][GNU Stow]] builds around the idea of one directory per prefix, and a
    symlink tree to create user environments
  - [[https://www.pvv.ntnu.no/~arnej/store/storedoc_6.html][STORE]] shares the same idea
  - [[https://live.gnome.org/OSTree/][GNOME's OSTree]] allows bootable system images to be built from a
    specified set of packages
  - The [[https://www.gnu.org/s/gsrc/][GNU Source Release Collection]] (GSRC) is a user-land software
    distribution; unlike Guix, it relies on core tools available on the
    host system
1-*- mode: org -*-
2
3[[https://www.gnu.org/software/guix/][GNU Guix]] (IPA: /ɡiːks/) is a purely functional package manager, and
4associated free software distribution, for the [[https://www.gnu.org/gnu/gnu.html][GNU system]]. In addition
5to standard package management features, Guix supports transactional
6upgrades and roll-backs, unprivileged package management, per-user
7profiles, and garbage collection.
8
9It provides [[https://www.gnu.org/software/guile/][Guile]] Scheme APIs, including a high-level embedded
10domain-specific languages (EDSLs) to describe how packages are to be
11built and composed.
12
13GNU Guix can be used on top of an already-installed GNU/Linux distribution, or
14it can be used standalone (we call that “Guix System”).
15
16Guix is based on the [[https://nixos.org/nix/][Nix]] package manager.
17
18
19* Requirements
20
21If you are building Guix from source, please see the manual for build
22instructions and requirements, either by running:
23
24 info -f doc/guix.info "Requirements"
25
26or by checking the [[https://guix.gnu.org/manual/en/html_node/Requirements.html][web copy of the manual]].
27
28* Installation
29
30See the manual for the installation instructions, either by running
31
32 info -f doc/guix.info "Installation"
33
34or by checking the [[https://guix.gnu.org/manual/en/html_node/Installation.html][web copy of the manual]].
35
36* Building from Git
37
38For information on building Guix from a Git checkout, please see the relevant
39section in the manual, either by running
40
41 info -f doc/guix.info "Building from Git"
42
43or by checking the [[https://guix.gnu.org/manual/en/html_node/Building-from-Git.html][web_copy of the manual]].
44
45* How It Works
46
47Guix does the high-level preparation of a /derivation/. A derivation is
48the promise of a build; it is stored as a text file under
49=/gnu/store/xxx.drv=. The (guix derivations) module provides the
50`derivation' primitive, as well as higher-level wrappers such as
51`build-expression->derivation'.
52
53Guix does remote procedure calls (RPCs) to the build daemon (the =guix-daemon=
54command), which in turn performs builds and accesses to the store on its
55behalf. The RPCs are implemented in the (guix store) module.
56
57* Contact
58
59GNU Guix is hosted at https://savannah.gnu.org/projects/guix/.
60
61Please email <[email protected]> for questions and <[email protected]> for bug
62reports; email <[email protected]> for general issues regarding the
63GNU system.
64
65Join #guix on irc.freenode.net.
66
67* Guix & Nix
68
69GNU Guix is based on [[https://nixos.org/nix/][the Nix package manager]]. It implements the same
70package deployment paradigm, and in fact it reuses some of its code.
71Yet, different engineering decisions were made for Guix, as described
72below.
73
74Nix is really two things: a package build tool, implemented by a library
75and daemon, and a special-purpose programming language. GNU Guix relies
76on the former, but uses Scheme as a replacement for the latter.
77
78Using Scheme instead of a specific language allows us to get all the
79features and tooling that come with Guile (compiler, debugger, REPL,
80Unicode, libraries, etc.) And it means that we have a general-purpose
81language, on top of which we can have embedded domain-specific languages
82(EDSLs), such as the one used to define packages. This broadens what
83can be done in package recipes themselves, and what can be done around them.
84
85Technically, Guix makes remote procedure calls to the ‘nix-worker’
86daemon to perform operations on the store. At the lowest level, Nix
87“derivations” represent promises of a build, stored in ‘.drv’ files in
88the store. Guix produces such derivations, which are then interpreted
89by the daemon to perform the build. Thus, Guix derivations can use
90derivations produced by Nix (and vice versa).
91
92With Nix and the [[https://nixos.org/nixpkgs][Nixpkgs]] distribution, package composition happens at
93the Nix language level, but builders are usually written in Bash.
94Conversely, Guix encourages the use of Scheme for both package
95composition and builders. Likewise, the core functionality of Nix is
96written in C++ and Perl; Guix relies on some of the original C++ code,
97but exposes all the API as Scheme.
98
99* Related software
100
101 - [[https://nixos.org][Nix, Nixpkgs, and NixOS]], functional package manager and associated
102 software distribution, are the inspiration of Guix
103 - [[https://www.gnu.org/software/stow/][GNU Stow]] builds around the idea of one directory per prefix, and a
104 symlink tree to create user environments
105 - [[https://www.pvv.ntnu.no/~arnej/store/storedoc_6.html][STORE]] shares the same idea
106 - [[https://live.gnome.org/OSTree/][GNOME's OSTree]] allows bootable system images to be built from a
107 specified set of packages
108 - The [[https://www.gnu.org/s/gsrc/][GNU Source Release Collection]] (GSRC) is a user-land software
109 distribution; unlike Guix, it relies on core tools available on the
110 host system