| 23 Nov 2025 |
 Sofie 🏳️⚧️ (she/her) | why did I even do that | 17:24:51 |
| Sofie 🏳️⚧️ (she/her) | to begin with | 17:24:54 |
| Sofie 🏳️⚧️ (she/her) | anyways | 17:24:56 |
| Sofie 🏳️⚧️ (she/her) | fixed now | 17:24:57 |
| Sofie 🏳️⚧️ (she/her) | we need an wasm build of lix!!!! /s | 17:25:08 |
 tebriel | when should I be using the other packages aside from lix in lixPackageSets? I'm unclear why they're in that namespace (maybe to give lix its expected verisons?) | 17:33:08 |
 whispers (it/fae) | if you use one of the packages in the set, then you want to use the lixPackageSets version. all it does is give the lix version of that package, which is sometimes just overriding the nix version to be lix nstead of cppnix and sometimes a full fork (as in the case of nix-eval-jobs) | 17:44:36 |
| whispers (it/fae) | the "advanced change" section on this page shows how to globally overlay them if you want to do that, but you can also just use them directly https://lix.systems/add-to-config/ | 17:45:25 |
| whispers (it/fae) | * if you use one of the packages in the set, then you want to use the lixPackageSets version. all it does is give the lix version of that package, which is sometimes just overriding the nix version to be lix nstead of cppnix and sometimes a full fork (as in the case of nix-eval-jobs). otherwise, it'll use cppnix internally | 17:47:26 |
| whispers (it/fae) | * | 17:51:22 |
| whispers (it/fae) | * if you use one of the packages in the set, then you want to use the lixPackageSets version. all it does is give the lix version of that package, which is sometimes just overriding the nix version to be lix nstead of cppnix and sometimes a full fork (as in the case of nix-eval-jobs). otherwise, each of those will use cppnix internally
(aiui the exceptions are aws-sdk-cpp, boehmgc, and editline, since those are internal to lix)
| 17:55:28 |
| whispers (it/fae) | * if you use one of the packages in the set, then you want to use the lixPackageSets version. all it does is give the lix version of that package, which is sometimes just overriding the nix version to be lix instead of cppnix and sometimes a full fork (as in the case of nix-eval-jobs). otherwise, each of those will use cppnix internally
(aiui the exceptions are aws-sdk-cpp, boehmgc, and editline, since those are internal to lix) | 22:52:35 |
| Sofie 🏳️⚧️ (she/her) | Does anyone have a ddc/ic kernel driver for Linux 6.17+ ?
I do not want to patch a kernel driver which used the legacy I2C_CLASS_DDC to use the newer i2c dev scan implementation 😭
| 23:35:51 |
| Sofie 🏳️⚧️ (she/her) | I see ,,,, you have to nowadays hook into DRM helpers to do the equilevevnt 😭 | 23:41:00 |
| Sofie 🏳️⚧️ (she/her) | I mean, I can implement it | 23:53:33 |
| 24 Nov 2025 |
 K900 | Lix 2.94 is in nixos-unstable-small now | 10:03:21 |
| K900 | Possibly also nixos-unstable but I have not checked | 10:03:28 |
|  Aijokey joined the room. | 10:19:53 |
 Coca | Not yet in nixos-unstable | 11:09:58 |
 Linux Hackerman | is it intentional that there's no tag in https://git.lix.systems/lix-project/nixos-module for 2.94.0? | 12:06:13 |
 niklaskorz | I think the module isn't meant to be used with stable versions anymore | 13:29:05 |
| niklaskorz | as mentioned on https://lix.systems/add-to-config/
Using the Lix NixOS module (only recommended for bleeding edge builds)
| 13:30:05 |
| 13 May 2024 |
|  zrsk joined the room. | 13:37:30 |
|  dariof4 joined the room. | 14:16:05 |
|  abbe joined the room. | 14:42:22 |
 mjm | lix is now in nixos-unstable, what's the best way to use it in a NixOS config? | 15:47:41 |
| K900 | nix.package = pkgs.lix | 15:47:54 |
| K900 | Probably | 15:47:58 |
| K900 | Or just keep using the module | 15:48:02 |
 puck | you can use nix.package = pkgs.lix; if you want; but using the overlay will guarantee more updates (tho less binary cache) | 15:48:44 |
