| 20 Dec 2025 |
piegames | now that you say all of this, maybe k900 has a point :p | 14:27:06 |
pentane | yeah I also agree with K900 | 14:27:51 |
pentane | another missing puzzle piece imo: currently, Nix treats the eval process and the build process as two conceptually separate things. But afaict there's nothing stopping us from treating the evaluation of, say, a flake as a derivation too - that derivation would have the flake source, its dependencies and nix as inputs, and output a .drv file | 14:30:22 |
pentane | once you've got it set up that way, IFD and dynamic derivations basically are the same thing | 14:31:10 |
pentane | and you get expression language agnosticism for free, since you can then use everything that produces .drv files as an expression language for Nix and not just Nixlang | 14:31:59 |
pentane | thank you for coming to my ted talk | 14:32:04 |
piegames | Basically from the eval side of things this will be a form of async, where eval halts when it needs the result of a derivation and proceeds once that derivation is built, comparable to waiting for IO | 14:33:01 |
piegames | TIL nix-build <nixpkgs> works even without --expr for some reason | 14:53:07 |
K900 | Attrset build target nonsense? | 14:53:39 |
K900 | Which is a thing you may actually want | 14:58:12 |
piegames | yes but | 15:02:40 |
Acid Bong | In reply to @piegames:flausch.social TIL nix-build <nixpkgs> works even without --expr for some reason because resolves into a filepath entry from NIX_PATH named abc
same thing as nix-build src/nixpkgs | 15:40:18 |
Acid Bong | * because `<abc>` resolves into a filepath entry from NIX_PATH named abc
same thing as `nix-build src/nixpkgs`
| 15:40:52 |
piegames | yes I understand that | 15:49:14 |
piegames | but I find this "fileish" thing weird | 15:49:53 |