README 4.8 KB

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