puck/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity

gesture at explanation of why binary caches exist

Browse source
This commit is contained in:
Adam Joseph 2022-08-05 10:33:48 -07:00
parent d5506aa712
commit 4de95f7f56
1 changed files with 6 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
doc/manual/src/package-management/terminology.md
View file

@ -18,10 +18,12 @@ commands from the `NixOS/nix` implementation.</sup>
directory on another machine, accessed via `ssh` or directory on another machine, accessed via `ssh` or
served by the `nix-serve` Perl script. served by the `nix-serve` Perl script.
A *binary cache* is a specialized Nix store whose metadata and A *binary cache* is a Nix store which uses a different format: its
signatures are kept in `.narinfo` files rather than in the Nix metadata and signatures are kept in `.narinfo` files rather than in a
database. Examples of binary caches include S3 buckets and the Nix database. This different format simplifies serving store objects
[NixOS binary cache](https://cache.nixos.org). over the network, but cannot host builds. Examples of binary caches
include S3 buckets and the [NixOS binary
cache](https://cache.nixos.org).
A *substituter* is a store other than `/nix/store` from which Nix will A *substituter* is a store other than `/nix/store` from which Nix will
copy a store path instead of building it. Nix will not copy a store copy a store path instead of building it. Nix will not copy a store