aboutsummaryrefslogtreecommitdiff
path: root/gnu/home.scm
diff options
context:
space:
mode:
authorZheng Junjie <zhengjunjie@iscas.ac.cn>2024-07-20 00:24:46 +0800
committerZheng Junjie <zhengjunjie@iscas.ac.cn>2024-08-01 23:44:38 +0800
commit33c111b032c581b41eafb4f55c185ff339ea69d7 (patch)
tree2c90cb5dc3aa6df284ba863933bee6151f159e35 /gnu/home.scm
parentfc9f19b7641be5701671df0a2f09f471de96e237 (diff)
downloadguix-33c111b032c581b41eafb4f55c185ff339ea69d7.tar.gz
guix-33c111b032c581b41eafb4f55c185ff339ea69d7.zip
gnu: kitemviews: Update to 6.4.0.
* gnu/packages/kde-frameworks.scm (kitemviews): Update to 6.4.0. Change-Id: Iad55a7475d883af0de07b8d8fc7f8eb156af3b7c
Diffstat (limited to 'gnu/home.scm')
0 files changed, 0 insertions, 0 deletions
generated by cgit
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
generated by cgit