| 28 Nov 2024 |
 ElvishJerricco | * You can avoid re-evaluating by setting pkgs in the nixosSystem call, I believe. Or by setting the nixpkgs.pkgs nixos option. Either of these will break anything in the nixpkgs.* nixos options (though I think that module yells at you about that now so it'll be obvious) | 13:40:16 |
| ElvishJerricco | that said, I'm not even sure nixpkgs eval is the slowest part tbh. NixOS module evaluation might be worse, and you're not going to get that to be shared | 13:41:15 |
 Leonardo Santiago | In reply to @elvishjerricco:matrix.org
that said, I'm not even sure nixpkgs eval is the slowest part tbh. NixOS module evaluation might be worse, and you're not going to get that to be shared I imagined it, which is sad. the design is pretty modular, as in, it should be able to evaluate the modules separately and then just re-use them for all configs. I was wondering if there was a way to restructure my code to do it like that. | 13:53:08 |
| ElvishJerricco | I mean that's not really possible | 13:53:36 |
| Leonardo Santiago | but I don't know enough about the internals of nix flake check for that | 13:53:37 |
| ElvishJerricco | any module can affect any other module arbitrarily | 13:53:43 |
| ElvishJerricco | so if two configs aren't literally exactly identical (I mean exactly) then there's basically zero potential for sharing | 13:54:20 |
| Leonardo Santiago | that is fair, I didn't think about that | 13:54:23 |
