gnu: git-annex: Patch 'git-annex webapp' to use hardcoded xdg-open. - guix

diff options

author	David Thompson <dthompson2@worcester.edu>	2023-01-06 16:06:47 -0500
committer	David Thompson <dthompson2@worcester.edu>	2023-01-08 13:25:34 -0500
commit	6ca59eec9ad8b63a5cbc12cb42ab8b1d6b08f116 (patch)
tree	063940354e21ac9c5ec9531cb670adc585f65f67 /etc
parent	8cca1a35bc42cddb7e0586062d192197520042d5 (diff)
download	guix-6ca59eec9ad8b63a5cbc12cb42ab8b1d6b08f116.tar.gz guix-6ca59eec9ad8b63a5cbc12cb42ab8b1d6b08f116.zip

gnu: git-annex: Patch 'git-annex webapp' to use hardcoded xdg-open.

* gnu/packages/haskell-apps.scm (git-annex)[arguments]: Add 'patch-webapp' phase. [inputs]: Add xdg-utils.

Diffstat (limited to 'etc')

0 files changed, 0 insertions, 0 deletions

f 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 [[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


context:
space:
mode: