From e9256952f16eb33f9b7e49777ec76878489a5053 Mon Sep 17 00:00:00 2001 From: tv Date: Fri, 13 Nov 2026 20:12:23 +0000 Subject: README: requirements, and where populate's program is New users learn what the deploying machine and the target need, including nixpkgs 23.11 or later for building populate, and developers where populate's program, its description, and its unit tests are. --- pkgs/populate/docs/design.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'pkgs/populate') diff --git a/pkgs/populate/docs/design.md b/pkgs/populate/docs/design.md index 44d8b21..7e68fdb 100644 --- a/pkgs/populate/docs/design.md +++ b/pkgs/populate/docs/design.md @@ -152,9 +152,9 @@ functions of krops. For a local target, populate runs commands directly. For a remote target, populate runs commands over ssh, sharing one master connection per target. The commands are fixed POSIX shell snippets, with values passed as positional arguments, so nothing gets quoted into them. -The target needs a POSIX shell, coreutils, findutils, rsync, Git for -`git` sources, and Nix for flakes; fresh installations of NixOS lack rsync -and Git. With `sudo`, the snippets run via `sudo`. +The target needs a POSIX shell, coreutils, findutils, rsync, `patch` for +patches, Git for `git` sources, and Nix; NixOS lacks Git. With `sudo`, +the snippets run via `sudo`. Populate runs rsync, Git, ssh, and Nix as programs, found in `PATH`. -- cgit v1.3.1