159dcc337a
Fixes <https://issues.guix.gnu.org/74832>. After update to guile-ssh 0.18.0, options passed to the `make-session' procedure now take precedence over the configuration file. In few places we however had code like `(or port 22)' leading to (in absence of alternative port being specified) always using port 22, ignoring the configuration file. Due to that for example following command fails: guix copy hello --to=name Name is reachable, but ssh server listens on port 2222. That is correctly configured in ~/.ssh/config, and the invocation used to succeed until the upgrade. However now it tries to connect to port 22 (since port was not specified). While setting the port on the command line *is* possible, it is not exactly ergonomic. Since guile-ssh (well, libssh) defaults to 22 if not told otherwise, we can just always pass the port, and #f will use the port from ~/.ssh/config or, iff none is set, 22. I went through the repository and adjusted all places where it seemed appropriate. In particular, these places were left alone: gnu/machine/digital-ocean.scm: The droplet is created with root user and the expected key, so forcing them to those values seems correct. gnu/machine/ssh.scm: For deployments reproducibility is favored over convenience, and user can pass #f to explicitly request using value the ~/.ssh/config. * guix/scripts/copy.scm (send-to-remote-host): Always pass the port to open-ssh-session. (retrieve-from-remote-host): Same. * guix/scripts/offload.scm (open-ssh-session): Pass #f as #:config. Skips reading the configuration file and is nicer. * guix/ssh.scm (open-ssh-session): Drop explicit parsing of the configuration since it is parsed by default. Report actual port used in the error message. * guix/store/ssh.scm (connect-to-daemon): Always pass the port part of the uri, even when #f. Change-Id: I5fdf20f36509a9a0ef138ce72c7198f688eea494 Reported-by: Dariqq <dariqq@posteo.net> Signed-off-by: Ludovic Courtès <ludo@gnu.org> |
||
|---|---|---|
| .forgejo | ||
| .mumi | ||
| build-aux | ||
| doc | ||
| etc | ||
| gnu | ||
| guix | ||
| m4 | ||
| nix | ||
| po | ||
| scripts | ||
| tests | ||
| .codespellrc | ||
| .dir-locals.el | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .guix-authorizations | ||
| .guix-channel | ||
| .mailmap | ||
| .patman | ||
| AUTHORS | ||
| bootstrap | ||
| ChangeLog | ||
| CODE-OF-CONDUCT | ||
| CODEOWNERS | ||
| config-daemon.ac | ||
| configure.ac | ||
| COPYING | ||
| gnu.scm | ||
| guix.scm | ||
| HACKING | ||
| Makefile.am | ||
| manifest.scm | ||
| NEWS | ||
| README | ||
| README.org | ||
| ROADMAP | ||
| THANKS | ||
| TODO | ||
- Requirements
- Installation
- Building from Git
- How It Works
- Contact
- Guix & Nix
- Related software
- Copyright Notices
-- mode: org --
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.
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://codeberg.org/guix/guix/.
Please email mailto:help-guix@gnu.org for questions. Bug reports should be submitted via https://codeberg.org/guix/guix/issues/. Email mailto: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
Copyright Notices
GNU Guix is made available under the GNU GPL version 3 or later license, and authors retain their copyright. For copyright notices, we adhere to the guidance documented in (info "(maintain) Copyright Notices"), and explicitly allow ranges instead of individual years. Here's an example of the preferred style used for copyright notices in source file headers:
Copyright © 2019-2023, 2025 Your Name <your@email.com>
Meaning there were copyright-able changes made for the years 2019, 2020, 2021, 2022, 2023 and 2025.