| 10 Dec 2025 |
 K900 | :) | 11:07:42 |
| 11 Dec 2025 |
|  Ivris joined the room. | 00:46:12 |
|  Ross joined the room. | 06:45:37 |
|  Cyrill joined the room. | 08:43:59 |
 Sofie 🏳️⚧️ (she/her) | So ugh | 10:38:00 |
| Sofie 🏳️⚧️ (she/her) | Anybody know something like flake-parts but which isn't owned (or at least, isn't a core contributor) by a self identified "anti woke" person like srid? | 10:38:58 |
 bandithedoge | flake-parts is owned by srid? | 11:38:39 |
| bandithedoge | either way, the best alternative to something like that is nothing at all imo | 11:39:22 |
 jappie | srid has 1 1-line commit in flake-parts as far as I can see 💀
https://github.com/hercules-ci/flake-parts/commit/34884706608919433ac07f09da18b32f6fde5dae | 11:42:48 |
| bandithedoge | In reply to @jappie:jappie.dev
srid has 1 1-line commit in flake-parts as far as I can see 💀
https://github.com/hercules-ci/flake-parts/commit/34884706608919433ac07f09da18b32f6fde5dae scandalous | 11:44:59 |
 P | In reply to @sofiedotcafe:matrix.org
Anybody know something like flake-parts but which isn't owned (or at least, isn't a core contributor) by a self identified "anti woke" person like srid? I'm glad I'm not the only one who got frustrated with that person. | 13:25:29 |
| K900 | I mean you are far from the only person | 13:25:52 |
| K900 | Given you know | 13:26:01 |
| K900 | Him being banned from the official spaces | 13:26:07 |
| bandithedoge | flake-parts is good though | 13:55:08 |
 teo (they/he) | it encourages people to use flakes though which is bad | 15:05:49 |
 neobrain | What do people like about flake-parts? Saw it mentioned a couple of times, but I find it difficult to extract anything meaningful out of their docs.
The perSystem stuff seems like a nice (if easily replaceable) utility, and besides that the docs mention modularity but then never actually explain what's different from vanilla flakes. | 15:22:09 |
| neobrain | * Why do people actually use flake-parts? Saw it mentioned a couple of times, but I find it difficult to extract anything meaningful out of their docs.
The perSystem stuff seems like a nice (if easily replaceable) utility, and besides that the docs mention modularity but then never actually explain what's different from vanilla flakes. | 15:23:42 |
 leona | you can actually spread outputs over multiple files with imports = [ ... ] which is way more complicated in raw flakes | 15:33:36 |
| leona | (you can achieve similar with e.g. lib.evalModules but that's more complex for my brain at least) | 15:34:50 |
| neobrain | Is imports specific to flake-parts? | 15:41:15 |
| neobrain | * Is imports specific to flake-parts?
I think I only used it when defining my Colmena hive, so I assumed it's a general nix thing | 15:42:03 |
| neobrain | * Is imports specific to flake-parts?
I think I only used it when defining my Colmena hive, so I assumed it's a general nix thing since I didn't need to pull in flake-parts explicitly | 15:42:22 |
| bandithedoge | the module system feels natural to anyone who's used nixos or home-manager | 17:04:28 |
| bandithedoge | and it actually feels like a specification with type checking instead of flake weirdness | 17:06:20 |
| bandithedoge | pretty sure it's part of lib.evalModules | 17:06:47 |
 Katalin 🔪 | it is | 17:37:18 |
| Katalin 🔪 | one of recent projects I used bare evalModules and it’s pretty nice | 17:39:00 |
| Katalin 🔪 | to build the flake outputs, that is | 17:39:31 |
| bandithedoge | honestly i'd love if nixpkgs had a single function that makes flakes module-based | 17:43:42 |
