| 30 Dec 2025 |
kdn | i need specialArgs in there to use my own modules | 19:43:47 |
kdn | there is no way to pass those in the built-in builder | 19:44:53 |
kdn | * there is no way to pass those in the built-in builder
maybe i'll just make an upstream patch to make those configurable | 19:45:37 |
kdn | * there is no way to pass those in the built-in builder
maybe i'll just make an upstream patch to make those configurable instead | 19:45:48 |
Winter | nix.linux-builder.config if you’re using nix-darwin, or pkgs.linux-builder.override (old: { modules = old.modules + [ … ]; }) otherwise | 19:46:42 |
Winter | you can use _module.args | 19:47:20 |
Winter | sorry, that first part of the answer was superfluous | 19:47:55 |
kdn | In reply to @winter:catgirl.cloud
nix.linux-builder.config if you’re using nix-darwin, or pkgs.linux-builder.override (old: { modules = old.modules + [ … ]; }) otherwise except i cannot pass my kdnConfig specialArg which i use to make OS/module-specific snippets and conditional imports | 19:48:11 |
Winter | _module.args doesn’t fit your needs? | 19:48:47 |
kdn | no, it cannot be used for conditional imports and pre-resolving snippets | 19:49:27 |