No description
Find a file
TakeV 6df695ae8f
Rename readme so that gitea will render it correctly
Change-Id: I6fcdc50089a06d0a99539831e47fc5cdbb9c6cac
2024-11-14 02:14:47 -05:00
.mumi
build-aux
doc doc: Fix `copy-recursively' arguments. 2024-11-12 23:29:09 +01:00
etc
gnu
guix ui: ‘show-what-to-build’ displays builds in topological order. 2024-11-12 23:46:52 +01:00
m4
nix
po
scripts
tests
.dir-locals.el .dir-locals.el: Add tempel snippets. 2024-09-21 11:05:36 -05:00
.editorconfig Add EditorConfig specification. 2022-11-05 11:26:55 +01:00
.gitattributes
.gitignore
.guix-authorizations add my keys to authorizations 2024-11-13 13:15:44 -05:00
.guix-channel
.mailmap
.patman
AUTHORS
bootstrap
ChangeLog build: Generate a ChangeLog file upon "make dist". 2013-05-12 16:35:17 +02:00
CODE-OF-CONDUCT CODE-OF-CONDUCT: Add a top notice. 2022-03-01 13:18:01 -05:00
config-daemon.ac
configure.ac
COPYING
gnu.scm
guix.scm
HACKING
Makefile.am gnu: Remove linux-libre 6.10. 2024-11-09 14:11:43 -05:00
manifest.scm
NEWS
README.org
ROADMAP
THANKS Thank Christine under her updated name. 2021-09-12 22:52:58 -04:00
TODO

-- mode: org --

Guix fork for personal use, for packages and modifications that are not in the mainline channel.

GNU Guix (IPA: ɡiːks) is a purely functional package manager, and associated free software distribution, for the 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 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 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 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 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 web_copy of the manual.

Authentication

Since this is a personal fork, the introduction commit is different.

For guix git authenticate, use:

  guix git authenticate 89e83088c1943f39bb479ebd1ae8c27f73b11a6c "1086 326D E207 068C 1C02  5129 A64F 4134 5C74 00AF"

To use it as a channel:

  (channel
   (name 'guix)
   (url "https://git.solarpunk.moe/TakeV/guix.git")
   (branch "main")
   (introduction
    (make-channel-introduction
     "89e83088c1943f39bb479ebd1ae8c27f73b11a6c"
     (openpgp-fingerprint
      "1086 326D E207 068C 1C02  5129 A64F 4134 5C74 00AF"))))

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 <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.

Guix & Nix

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.

Related software

  • 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