You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
* guix/utils.scm (base16-string->bytevector): New procedure. * tests/utils.scm ("bytevector->base16-string->bytevector"): New test.
|10 years ago|
|guix||10 years ago|
|srfi||10 years ago|
|tests||10 years ago|
|.gitignore||10 years ago|
|AUTHORS||10 years ago|
|COPYING||10 years ago|
|README||10 years ago|
|guix.scm||10 years ago|
-*- mode: org -*-
Guix is Nix from Guile!
Concretely, it allows Nix package management to be done entirely in
Scheme. The goal is to investigate whether Scheme, and in particular
the ability to define EDSLs, would allow it to fulfill the role of the
Guix currently depends on the following packages:
- GNU Guile 2.0.x, http://gnu.org/software/guile/
- Nix, http://nixos.org/nix/
- libchop, http://nongnu.org/libchop/
For bootstrapping purposes, it is useful to reuse packages from Nixpkgs.
For this to work, you need to have a checkout of the Nixpkgs repository,
with the `NIXPKGS' environment variable pointing to it.
- Nixpkgs, http://nixos.org/nixpkgs/
* 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
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.
The repository is at <https://gitorious.org/guix/>.
Please email <firstname.lastname@example.org> or <email@example.com>, or
join #guile or #nixos on irc.freenode.net or `civodul'.