flakelight | 38 Members | |
| https://github.com/nix-community/flakelight | 12 Servers |
| Sender | Message | Time |
|---|---|---|
| 29 Sep 2025 | ||
| It does work, if I try to access it in pkgs:
| 15:48:59 | |
| * It does work, if I try to access it in pkgs: (That is only possible in a nixosModule)
| 15:51:50 | |
| * It does work, if I try to access it in pkgs: (That is possible in a nixosModule, and not in nixosConfigurations)
| 15:52:12 | |
Other than this toy example, the thing I'm trying to do is to add helper functions like mkBaseSystem, mkTestSystem, 'mkCalibSystem', that can be used to generate nixosConfigrations. | 15:57:16 | |
* Other than this toy example, the thing I'm trying to do is to add helper functions like mkBaseSystem, mkTestSystem, mkCalibSystem, that can be used to generate nixosConfigrations. | 15:57:30 | |
| right, the overlays applies for lib in pkgs; the one for module args is set by the module system. not sure if tge module system allows modifying it | 16:08:13 | |
but _module.args.noverby would allow you to get { noverby, ... } from modules | 16:09:49 | |
| ill check if itd be possible to modify the module lib (though might be an infinite recursion thing) | 16:10:36 | |
especially since lib is specialArgs not args | 16:11:09 | |
ah right, i'd been using self.lib in the past iirc | 16:12:35 | |
* Other than this toy example, the thing I'm trying to do is to add helper functions like mkBaseSystem, mkTestSystem, mkCalibSystem, that can be used to generate nixosConfigurations. | 16:28:31 | |
| 30 Sep 2025 | ||
| How does that work? | 05:30:35 | |
you can set a flakes lib output, and then access it though inputs.self | 05:35:43 | |
| though if you have a lot of flakes, it probably better to have a shared flake dep that exports a lib for everything else to use | 05:36:40 | |
If you put lib functions into nix/lib, then I guess you cannot currently access module args? | 08:11:27 | |
* If you put lib functions as standalone nix files into nix/lib, then I guess you cannot currently access module args? | 08:12:17 | |
| E.g | 08:14:31 | |
Download image.png | 08:14:32 | |
You can only access module args, if you create a nix/lib.nix instead? | 08:21:26 | |
* So you can only access module args, if you create a nix/lib.nix instead? | 11:26:10 | |
yeah, youd need nix/lib.nix or nix/lib/default.nix | 16:13:02 | |
| lib is an attrset of anything at all so cant add optional args to anything but the root attrset | 16:14:40 | |
| 2 Oct 2025 | ||
| Did you come to a conclusion for this? | 09:28:05 | |
| Ended up using this, but it would be nice if there was a clean way to extend lib in module args:
| 09:43:12 | |
| Where are you supposed to add helper functions similar to
I cannot put it under
| 10:03:53 | |
| * Where are you supposed to add helper functions similar to
I cannot put it under
| 10:04:10 | |
| * Where are you supposed to add helper functions similar to
I cannot put it under
| 10:06:13 | |
| * Where are you supposed to add helper functions similar to
I cannot put it under
| 10:06:45 | |
| ah, the correct places would either be lib, legacyPackages, or an overlay | 14:53:12 | |
id normally set <namespace>.mkShell in an overlay output and add that to withOverlays | 14:54:21 | |