| 7 Apr 2026 |
 accelbread | is there docs for repl-overlays? can't seem to find anything | 17:38:10 |
 llakala | In reply to @accelbread:matrix.org
is there docs for repl-overlays? can't seem to find anything there's a release note | 17:38:23 |
 zoë (she/her) | one thing i could probably do at least is make soles aloases for lib.evalModules { modules = [...]; }, as well as the entry points for nixos and hm, because it's so annoying to type and remember everytime | 17:38:29 |
| zoë (she/her) | yeah basically just a release note and an entry in the nix.conf manual | 17:38:47 |
| zoë (she/her) | * | 17:38:54 |
| llakala | https://docs.lix.systems/manual/lix/stable/release-notes/rl-2.90.html | 17:38:56 |
| llakala | In reply to @llakala:matrix.org
https://docs.lix.systems/manual/lix/stable/release-notes/rl-2.90.html i don't think theres subheading links but it's here | 17:39:10 |
| accelbread | nice, I'll have to play around with it | 17:39:36 |
| zoë (she/her) | https://docs.lix.systems/manual/lix/2.90/command-ref/conf-file.html#conf-repl-overlays | 17:39:39 |
| zoë (she/her) | here's the nix.conf part | 17:39:44 |
| zoë (she/her) | * | 17:39:55 |
| llakala | repl-overlays was actually originally proposed as a cppnix feature and got bikeshedded by roberth and others for not being flakey enough | 17:40:04 |
| zoë (she/her) | (and next release, nix repl --help will also have a section about them :p) | 17:40:38 |
| llakala | In reply to @llakala:matrix.org
repl-overlays was actually originally proposed as a cppnix feature and got bikeshedded by roberth and others for not being flakey enough see https://github.com/NixOS/nix/pull/10203 | 17:41:05 |
| llakala | a very depressing issue to read through | 17:41:27 |
|  @vigress9:matrix.org removed their display name V. 🏳️⚧️. | 17:46:14 |
| @vigress9:matrix.org left the room. | 17:47:05 |
 kfiz | Fair enough. | 18:30:30 |
 maralorn | Huh, hydra was running on lix for a while now? Any lessons learned from that? | 21:52:45 |
 raitobezarius | what lesson? | 21:59:01 |
| maralorn | Something between "the evaluator regularly crashed" and we saved tons of money because we could switch to a machine with much less ram. 😆 | 22:01:51 |
| raitobezarius | i surmise that lix is currently less interesting at scale than cppnix given there's still optimizations we are not doing | 22:02:53 |
 delroth | the builders run on lix, not the coordinator | 22:03:19 |
| raitobezarius | the last time lix was used for a long time on the hydra build farm, i remember it was in response of a consistently crashing cppnix interpreter | 22:03:22 |
 Jules Lamur | Hey, I don't understand why a nix-store -qR --include-outputs on a deriver does not include the outputs of dependencies.
Could you help me understand what's happening and if that's the expected behavior?
Basically, the question is why does the last command not contains the output of bison (only the deriver)?
$ nix-instantiate --eval https://releases.nixos.org/nixos/25.11-small/nixos-25.11.8880.5a035534a428/nixexprs.tar.xz -A hello.drvPath --raw
/nix/store/0a8f9vx5sdwdx4a27axfkkjznj5navrq-hello-2.12.2.drv
$ nix-store -q -R --include-outputs /nix/store/0a8f9vx5sdwdx4a27axfkkjznj5navrq-hello-2.12.2.drv | grep bison
/nix/store/vgjfnqbxgxa8a5575bhq07nm35b2l31m-bison-3.8.2.tar.gz.drv
/nix/store/i7miyh7832lkyy229nipb5h6zg5n32rc-bison-3.8.2.drv
Does that even make sense to have a dependency on a deriver but not on its output?
| 22:14:44 |
| raitobezarius | the recipe depends on the recipes of others, but not the outputs of others except if the recipe depends on the actual output to build itself | 22:19:16 |
| raitobezarius | the output depends on the outputs of others, including the recipes | 22:19:22 |
| raitobezarius | i'm not sure there's "one" good model of dependencies for .drv files | 22:20:56 |
| raitobezarius | .drv files in the store are already an hack somewhat | 22:21:03 |
| raitobezarius | one advantage i see not to make the bison output appear in that list is that this probably has consequences for nix copy | 22:21:36 |
