| 1 Feb 2024 |
 infinisil | Ahh! The problem is that config.user doesn't contain any mkForce anymore. It's an evaluated option, so all of those modifiers are gone | 20:39:01 |
| infinisil | So the input to user is lib.mkForce { b = 3; }, but it outputs just { b = 3; }, no conflict there, since there's just one definition | 20:39:48 |
| infinisil | Similarly the input to defaults is just that one default = { a = 1; b = 2; } (which is actually defaults = lib.mkOptionDefault { ... } but that's not relevant here), it outputs { a = 1; b = 2; } | 20:40:38 |
| infinisil | Finally, you have effectively
{
out = lib.mkMerge [
config.default
config.user
];
}
| 20:41:10 |
| infinisil | * Finally, you have effectively
{
out = lib.mkMerge [
{ a = 1; b = 2; }
{ b = 3; }
];
}
Both of which are without priority, so it recurses into the attrs and conflicts because two bs
| 20:41:59 |
| infinisil | Instead if you want to actually copy the definitions from one option to another, the mkAlias function suite is what you need: https://github.com/NixOS/nixpkgs/blob/master/lib/modules.nix#L1039-L1073 | 20:43:19 |
| infinisil | * Instead if you want to actually copy the definitions from one option to another, the mkAlias function suite is what you need: https://github.com/NixOS/nixpkgs/blob/a0d3f10c751b6b2642b44d327470f68ad6bc7952/lib/modules.nix#L1039-L1073 | 20:43:32 |
| 2 Feb 2024 |
 djacu | Ah that's a pretty sweet suite. Just so I understanding you completely, you're just mentioning this for other use cases. Not suggesting that it could be used in the example I provided? | 00:45:43 |
| infinisil | That alias stuff is pretty messy, I wouldn't recommend that myself, but sometimes it is needed. In this case the simpler mapAttrs (name: mkDefault) works though | 02:53:43 |
|  ibizaman joined the room. | 05:25:20 |
|  sarcasticadmin joined the room. | 20:01:14 |
| 5 Feb 2024 |
|  hexa joined the room. | 01:34:42 |
| 8 Feb 2024 |
|  zrsk joined the room. | 10:38:02 |
| 15 Feb 2024 |
|  a-kenji joined the room. | 19:15:14 |
| 16 Feb 2024 |
|  Qyriad joined the room. | 14:56:15 |
|  mr-qubo joined the room. | 14:59:24 |
| mr-qubo | I recently stumbled upon similar issue when working on home-manager. https://discourse.nixos.org/t/is-it-possible-to-define-systemd-services-in-a-submodule/39538/5
The idea is that enabling https://nix-community.github.io/home-manager/options.xhtml#opt-programs.bash.enableCompletion should set environment.pathsToLink = [ "/share/bash-completion" ];.
I think that module system is missing an option to pass config options recursively up to all ancestors.
| 15:06:01 |
| mr-qubo | My idea is that nixos config could have a property extraNixosChildConfig and in home-manager bash module I could set _recurseAncestors = { extraNixosChildConfig = { environment.pathsToLink = [ ... ]; }; }. | 15:07:22 |
| mr-qubo | wdyt? | 15:07:26 |
| mr-qubo | * My idea is that nixos config could have a property extraNixosChildConfig that gets merged with the rest of the config and in home-manager bash module I could set _recurseAncestors = { extraNixosChildConfig = { environment.pathsToLink = [ ... ]; }; }. | 15:07:44 |
| mr-qubo | * My idea is that nixos config could pick up extraNixosChildConfig from childs and merge it with the rest of the config and in home-manager bash module I could set _recurseAncestors = { extraNixosChildConfig = { environment.pathsToLink = [ ... ]; }; }. | 15:08:21 |
| infinisil | Not sure about that recursive thing, that doesn't seem necessary, but yeah if there's something missing in the NixOS module for home-manager, that could be added | 15:34:09 |
| infinisil | Sounds like an issue for the home-manager repo | 15:34:16 |
| mr-qubo | Yeah, we could add it just for home-manager. But is seems like the issue is quite generic. See also https://github.com/NixOS/nixpkgs/pull/152785. | 15:51:50 |
| infinisil | Hmm yeah fair. I don't have the capacity to think a lot about this right now, it's a very intricate topic to wrap ones head around | 15:56:55 |
