| 11 Dec 2025 |
 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 |
