NixOS/Nix/Nixpkgs/Nix* slang terms and common abbreviations
See the Nix glossary: https://nixos.org/manual/nix/unstable/glossary.html
Nix* specific abbreviations
| Abbreviation |
Full version |
Explanation |
Link
|
| CA |
Content-addressed |
If a derivation is Content Addressed it means that the hashes in the paths of its outputs are generated by the outputs contents. |
Ca-derivations
|
| FOD |
Fixed output derivation |
A derivation where it is ensured by means of a hash that the output is fixed. Often, these are source tarballs. |
|
| IFD |
Import From Derivation |
Using the result of a derivation in a nix expression. |
https://blog.hercules-ci.com/2019/08/30/native-support-for-import-for-derivation/
|
| NUR |
Nix User Repository |
A community driven meta-repository of user maintained packages. |
https://github.com/nix-community/NUR
|
| ZHF |
Zero hydra failures |
As part of the release cycle, there is a time where nixpkgs maintainers try to minimise the number of build errors. ZHF is the goal of this process.
|
Non-Nix* specific abbreviations that are used heavily in the Nix* ecosystem
| Abbreviation |
Full version |
Nix*-specific explanation
|
| r13y |
Reproducibility |
The same derivation should produce the same output every time it is instantiated
|
| TOFU |
Trust on first use |
Trust the hash of a source for the first time when you fetch it, and fix it in the nix expression
|
| LGTM |
Looks Good To Me |
Often left as a comment on PRs
|
