Go to file
Ludovic Courtès 2d34fa4902 Update `TODO'. 2012-12-09 14:44:17 +01:00
build-aux distro: Rebuild bootstrap Binutils and GCC. 2012-11-16 00:26:34 +01:00
distro/packages distro: Add ACL. 2012-12-07 22:32:00 +01:00
doc doc: Mention the pronunciation of "Guix". 2012-11-25 16:08:10 +01:00
guix Add (guix licenses). 2012-12-08 19:17:02 +01:00
m4 build: Require GNU libgcrypt. 2012-11-03 21:49:54 +01:00
po distro: Go for one module per package. 2012-11-04 21:46:14 +01:00
srfi SRFI-64: Remove use of (ice-9 syntax-case). 2012-06-05 11:21:13 +02:00
tests derivations: Fix erroneous call to `add-to-store' for local files as input. 2012-12-04 23:46:50 +01:00
.dir-locals.el Add (guix ui). 2012-11-01 00:52:44 +01:00
.gitignore Add (guix snix) and the `guix-import' command. 2012-11-04 19:38:31 +01:00
AUTHORS Change email address in `AUTHORS'. 2012-12-09 14:42:30 +01:00
COPYING Add the usual top-level files. 2012-06-03 23:46:56 +02:00
ChangeLog build: Use Automake's `gnu' option. 2012-07-07 22:53:01 +02:00
HACKING doc: Document basic package definitions. 2012-11-21 15:56:43 +01:00
Makefile.am Add (guix licenses). 2012-12-08 19:17:02 +01:00
NEWS build: Use Automake's `gnu' option. 2012-07-07 22:53:01 +02:00
README doc: Mention the pronunciation of "Guix". 2012-11-25 16:08:10 +01:00
ROADMAP doc: Add `ROADMAP'. 2012-11-18 17:56:02 +01:00
THANKS Add `THANKS'. 2012-07-07 22:39:57 +02:00
TODO Update `TODO'. 2012-12-09 14:44:17 +01:00
configure.ac build: Change bug-report address; add URL. 2012-11-24 00:36:36 +01:00
distro.scm distro: Search bootstrap binaries and patches in %LOAD-PATH. 2012-11-25 16:28:52 +01:00
guix-build.in guix-build: Don't connect to the daemon when run with `--version' or `--help'. 2012-12-04 23:50:20 +01:00
guix-download.in guix-download: Use code from (guix build download). 2012-11-13 23:04:21 +01:00
guix-import.in Add (guix snix) and the `guix-import' command. 2012-11-04 19:38:31 +01:00
guix-package.in guix-package: Extract version strings when installing a direct store path. 2012-11-19 23:53:32 +01:00
guix.scm Remove (guix http) and (guix ftp). 2012-11-13 00:23:39 +01:00
hydra.scm build: Have `hydra.scm' return one job per package. 2012-11-25 17:12:46 +01:00
pre-inst-env.in distro: Search bootstrap binaries and patches in %LOAD-PATH. 2012-11-25 16:28:52 +01:00
release.nix release.nix: Pass `--with-libgcrypt-prefix' in the `tarball' job. 2012-11-04 13:03:15 +01:00

README

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

-*- mode: org -*-

[[http://www.gnu.org/software/guix/][GNU Guix]] (IPA: /ɡiːks/) is a purely functional package manager, and
associated free software distribution, for the [[http://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 [[http://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.

A user-land free software distribution for GNU/Linux comes as part of
Guix.

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


* Hacking

GNU Guix currently depends on the following packages:

  - [[http://gnu.org/software/guile/][GNU Guile 2.0.x]]
  - [[http://nixos.org/nix/][Nix]]
  - [[http://gnupg.org/][GNU libgcrypt]]

Optionally, packages from Nixpkgs may be transparently reused from Guix.
For this to work, you need to have a checkout of the Nixpkgs repository;
the `--with-nixpkgs' option allows you to let `configure' know where the
Nixpkgs checkout is.

  - [[http://nixos.org/nixpkgs/][Nixpkgs]]

When building Guix from a checkout, the following packages are also
required:

  - [[http://www.gnu.org/software/autoconf/][GNU Autoconf]]
  - [[http://www.gnu.org/software/automake/][GNU Automake]]
  - [[http://www.gnu.org/software/gettext/][GNU Gettext]]

The "autoreconf -vi" command can be used to generate the build system
infrastructure; it reports an error if an inappropriate version of the
above packages is being used.

* 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
=/nix/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 Nix daemon (the
=nix-worker --daemon= command), which in turn performs builds and
accesses to the Nix 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 <bug-guix@gnu.org> for bug reports or questions regarding
Guix and its distribution; email <gnu-system-discuss@gnu.org> for
general issues regarding the GNU system.

Join #guix on irc.freenode.net.

* Guix & Nix

GNU Guix is based on [[http://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 [[http://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

  - [[http://nixos.org][Nix, Nixpkgs, and NixOS]], functional package manager and associated
    software distribution, are the inspiration of Guix
  - [[http://www.gnu.org/software/stow/][GNU Stow]] builds around the idea of one directory per prefix, and a
    symlink tree to create user environments
  - [[http://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 [[http://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