#nix

notashelf.dev

Nix Evaluation Is a Scheduling Problem

fzakaria.com

Super Mario Derivations

One of the most surprising aspects of the Nix language is that it is lazy, especially if you have never used a lazy language before. This laziness is what makes much of Nixpkgs possible, and its complexity.

discourse.nixos.org

Refrencing files with ./path/to/foo - am I holding it wrong?

This one got me off guard. Been on nixos for several years now, and I always relied on files referenced by ./path/to/foo.env being available on the target machine. tl;dr - I believe there’s a few potential non-obvious things going on in here: files referenced with ./path/to/foo.env not being copied to remote nixos VMs opaquely accessing host’s /nix/store oci-containers’s environmentFiles too lazily evaluated (or not at all) The other day I was setting up managed containers via oci-containe...

jezenthomas.com

Nix Overrides That Expire Themselves

Package overrides in a Nix flake tend to outlive the problem they were written to solve. A small trick with lib.warnIf makes an override announce when nixpkgs has caught up and the override can be deleted.

domenkozar.com

nixpkgs has a due-process problem

Three cases where Nixpkgs exercised power without clear rules: a commit-bit removal, a pull request closed by headcount, and a review blocked indefinitely.

domenkozar.com

nixpkgs has a due-process problem

Three cases where Nixpkgs exercised power without clear rules: a commit-bit removal, a pull request closed by headcount, and a review blocked indefinitely.

github.com

GitHub - wavelens/gradient: nix-based continuous integration system

nix-based continuous integration system. Contribute to wavelens/gradient development by creating an account on GitHub.

fzakaria.com

The Nix sandbox is a hidden input

The whole beauty of Nix was that it was incredibly pragmatic to achieve “reproducibility”, which is quite an overloaded term. The default model for Nix is the intensional-model which is input-addressed: the hash of a store path is derived from the recipe (derivation) that produced it, and not the bytes that came out of it. In that framing Nix achieves repeatability. Nix, by default, was never bit-for-bit reproducible.1 Nix has a ca-derivations feature that makes the output path a hash of the output bytes, which is a different model (extensional-model). ↩