| 17 Dec 2025 |
 piegames | I'll try to get back to this with priority once git.lix.systems is up again | 21:54:05 |
| 18 Dec 2025 |
 KFears (they/them) | Thanks team for the work on distributed builds and related documentation!
The legacy format is confusing and restraining as fuck. It is highly impressive how there's a very graceful migration path towards the better machines.toml format, and the documentation is very descriptive, precise and non-ambiguous. I remember setting up distributed builds before and it was one hell of an experience; now, I've read the new documentation page and I'm fully confident I can get it to work with minimal effort, even if some sections required a careful re-read due to the mental complexity of the old system
Thank you! <3 | 02:49:59 |
 blitz | oh nice! what changed? does anyone have a link? | 07:32:10 |
 Rutile (Commentator2.0) feel free to ping | we now support declaring remote builders using a toml file instead of the weird space (or semicolon) seperated mess the old foramt was | 09:29:21 |
 Qyriad | it also accepted semicolons??? wtf | 10:14:23 |
 niko ⚡️ | I also never knew it accepted semicolons I just thought everything was delimited by whitespace | 10:19:36 |
 Lotte (it/its)/Cinny (she/her) | oh what | 10:28:06 |
| Rutile (Commentator2.0) feel free to ping | yeeeep
there is some other cursed stuff in there too | 10:32:43 |
| Rutile (Commentator2.0) feel free to ping | though iirc semicolon only instead of newline | 10:33:01 |
 kloenk | exactly my reaction while reading | 10:39:55 |
| Rutile (Commentator2.0) feel free to ping | :D | 10:40:19 |
 helle (just a stray cat girl) | at this point, the horrors of the inherited code base have stopped to amaze me | 10:42:49 |
| helle (just a stray cat girl) | which means I haven't dug deeply enough for some of them | 10:44:48 |
| Rutile (Commentator2.0) feel free to ping | for (auto line : tokenizeString<std::vector<std::string>>(builders, "\n;"))
:D
| 10:44:50 |
| Rutile (Commentator2.0) feel free to ping | if i read things correclty, one could use \r instead of a space too | 10:46:28 |
| helle (just a stray cat girl) | I've been more shocked at erm, some of the quality libraries we are using | 10:46:46 |
 Sofie 🏳️⚧️ (she/her) | oo :3 | 13:03:15 |
| Rutile (Commentator2.0) feel free to ping | what does nix-build --temp-dir some/path do? | 15:19:44 |
| Rutile (Commentator2.0) feel free to ping | it seems to be documented absolutely nowhere | 15:20:17 |
| kloenk | The question of do I want to know the probably cursed detail or better not read the chat :p | 15:20:42 |
 rosssmyth | If I had to guess, it set the build dir to the path specified rather than whatever it is by default (something like /nix/var/nix/blah/blah/blah iirc) | 16:15:28 |
| rosssmyth | does not seem to be the answer | 16:16:54 |
| rosssmyth | (tried with nix build --temp-dir ~/tempdir --keep-failed --rebuild with a derivation I knows) | 16:17:31 |
| rosssmyth | * (tried with nix build --temp-dir ~/tempdir --keep-failed --rebuild with a derivation I know fails) | 16:17:42 |
 Marie | what the heck is error: lock file contains mutable lock '{"path":"contrib/nix/dev","type":"path"}'
is this a cppnix divergence? | 16:41:21 |
 K900 | Yes | 17:03:46 |
| K900 | Something about subflake paths | 17:03:50 |
 guiniol | Does anyone have experience running NixOS on tight eMMC spaces? I am considering a Zimaboard as a remote backup option (it would only run ssh+tailscale and receive ZFS snapshots), and I am worried about the limited 32GB of eMMC that the system needs to fit on. Builds would have to be remote but that shouldn't be an issue since I have a powerful enough server running NixOS already. | 19:21:27 |
| K900 | Would maybe look into something like a CM3588 NAS KIT though | 19:22:56 |
| K900 | Gets you mostly the same form factor at like a third of the cost | 19:23:06 |
