| 8 Sep 2025 |
 Sandro 🐧 | Did you try?
nixVersions = prev.nixVersions.extend (final: prev:
nixComponents_2_31 = prev.nixComponents_2_31.overrideScope (finalScope: prevScope: { stdenv = pkgs_25_05.clangStdenv; };
};
| 14:37:21 |
 oddlama | Yes that is looking good, thanks. Is this the preferred way to do overrides for those types of packages now? | 15:35:33 |
 Sergei Zimmerman (xokdvium) | In reply to @oddlama:matrix.org
Yes that is looking good, thanks. Is this the preferred way to do overrides for those types of packages now? For the modular packaging - yes. Since now this is not a monolithic package that you can override | 16:04:22 |
| Sandro 🐧 | Also an example on how to add patches
nixComponents_2_31 = (prev.nixComponents_2_31.overrideScope (finalScope: prevScope: {
aws-sdk-cpp = null;
boost = boost231;
withAWS = false;
})).appendPatches (commonPatches ++ [
./nix-derivation-better-copy-2.30.diff
]);
| 16:05:49 |
| 9 Sep 2025 |
 Winter | this is seemingly missing where commonPatches comes from fyi | 02:21:31 |
| Sandro 🐧 | * Also an example on how to add patches
nixComponents_2_31 = (prev.nixComponents_2_31.overrideScope (finalScope: prevScope: {
aws-sdk-cpp = null;
boost = boost231;
withAWS = false;
})).appendPatches [
./nix-derivation-better-copy-2.30.diff
];
| 08:50:38 |
| Sandro 🐧 | That's just a list I have somewhere above in a let in | 08:50:56 |
|  aciceri changed their display name from zrsk to aciceri. | 15:02:57 |
| Sergei Zimmerman (xokdvium) | Curiously, Boehm granule size on 64 bit systems is 16 bytes. That means that 16 byte atomics for Value are very workable, since x86_64 needs stuff to be 16 bytes aligned (otherwise memory might straddle the cache line and that won’t be atomic ever) | 17:31:17 |
| 10 Sep 2025 |
|  SomeoneSerge (back on matrix) changed their display name from SomeoneSerge (@nixcon & back on matrix) to SomeoneSerge (back on matrix). | 00:34:03 |
|  @nerves:bark.lgbt left the room. | 12:31:49 |
|  Hierophilos joined the room. | 14:18:45 |
|  matthewcroughan changed their display name from matthewcroughan @ nixcon to matthewcroughan. | 14:56:12 |
|  connor (he/him) (UTC-7) changed their display name from connor (he/him) (UTC+2) to connor (he/him) (UTC-7). | 22:20:37 |
| 11 Sep 2025 |
|  Preston joined the room. | 17:06:14 |
| 12 Sep 2025 |
|  getchoo joined the room. | 00:07:47 |
| getchoo | hey Mic92: just came across your comment on the detnix installer thread. i'm not super familiar with the codebase just yet, but i have a good bit of experience with gha and ci janitor work, and would love to help out if i can! :) | 00:16:11 |
| Sergei Zimmerman (xokdvium) | Here are some notes from our meeting with the installer team. I forgor to publish them to discourse https://pad.lassul.us/KgpbqiQpQEOX2cKF5Ehjwg# | 00:24:04 |
| Sergei Zimmerman (xokdvium) | Very incomplete and half-way | 00:24:49 |
| Sergei Zimmerman (xokdvium) | But basically it'd be great to start integrating it into our dogfooding setup https://github.com/NixOS/nix/blob/master/.github/actions/install-nix-action/action.yaml | 00:25:28 |
| Sergei Zimmerman (xokdvium) | PoC for 16 byte atomics on x86_64 for paralell eval: https://github.com/NixOS/nix/pull/13964. Lovers of compiler intrinsics are welcome | 01:07:35 |
|  @jordanjoel1:matrix.org changed their profile picture. | 03:27:09 |
| @jordanjoel1:matrix.org left the room. | 03:34:24 |
|  Pratham Patel joined the room. | 04:41:40 |
| getchoo | thanks for the link! i'll take a closer look at some of the stuff mentioned and what's already there this weekend hopefully (new job has had me a bit busy, catching covid from it didn't help either 😆), but i definitely think i can get this dogfooding setup going. i already have a bit of experience with very similar things in other action projects | 05:01:36 |
 jaen | If there are other tasks that can be done in parallel for installer upstreaming I'd also be interested — I was cooking a Nix article series for $CURRENT_JOB blog (the company does a lot of Bazel, so it's structured by way of compare & contrast) and don't feel comfortable publishing them until after the installer situation is resolved, I don't really want to redirect people away from the upstream. | 11:27:06 |
 magic_rb | As many before me, i implemented my own very basic nix evaluator, it doesnt have any builtins right now, only does basic arithmetic. But the point of it is that it doesnt use AST walking, but rather an approach similar to the STG. Its not fully tagless unfortunately, but i think im just missing something. Anyway, it only makes sense to develop it further if its faster than nix/lix so im wondering if its possible to formulate micro benchmarks relying on a subset of the nix language which could tell me whether my impl is faster or not. Anyone has thought about this before? | 15:07:03 |
| magic_rb | I dont want to write a full nix impl only to figure out "its horribly slow and nothing can be done about that". Ideally we'd be able to tell way before i implement all the nixisms | 15:08:27 |
| magic_rb | https://git.redalder.org/magic_rb/nix-stg oh and the code | 15:11:23 |
| magic_rb | The evaluator is currently recursive but thats my mistake, i just need to do while !iptr.is_whnf() iptr.force() | 15:12:22 |
