| 14 Jan 2026 |
 bake.monorail |
builtins.unsafeGetAttrPos
:O :O :O
| 20:46:55 |
| 17 Jan 2026 |
 Majiir Paktu | I can set internal on an option to make it usable only in nixpkgs. Is there any mechanism to do the opposite, where an option is unusable in-tree but still available to users? The use case is for an option that should be deprecated, but where the replacement is not yet stable enough to produce a warning and steer users toward it. But also, the replacement is widely used within nixpkgs already. | 02:25:32 |
 hexa | warnings | 02:27:04 |
 Matt Sturgeon | internal doesn't not affect who can use an option. It only affects whether it is documented. It's effectively the same thing as visible = "shallow". | 12:30:52 |
| Matt Sturgeon | * internal doesn't affect who can use an option. It only affects whether it is documented. It's effectively the same thing as visible = "shallow". | 13:05:04 |
| 18 Jan 2026 |
|  ·☽•Nameless☆•777 · ± changed their profile picture. | 14:58:52 |
|  isabel changed their profile picture. | 20:43:36 |
| 19 Jan 2026 |
|  mpuppe joined the room. | 21:20:37 |
| 21 Jan 2026 |
| bake.monorail | is there anything more specific than types.str I can use for a version number that I will later compare with lib.versionAtLeast? | 20:39:57 |
| Matt Sturgeon | In string types we have strMatching, however that expects a regex not a predicate function.
The general solution is addCheck (see extending types), however the examples there don't show that you typically also want to extend/override the type's description. | 20:46:28 |
| bake.monorail | yeah, I went with strMatching, but I was hoping to have a type matching exactly what versionAtLeast would accept, but I guess there's no such a thing | 20:50:21 |
| bake.monorail | versionAtLeast under the hood uses builtins.compareVersions, which seems to accept anything, probably it has a last-resort method comparison that's just lexicographic comparison | 20:53:24 |
| 22 Jan 2026 |
 nbp | I would say, at the very least types are part of the documentation, if you can give a more descriptive name even if there is no additional check, this might be worth it. (i-e. just aliasing the name my motivate someone else to add a check function later) | 11:28:54 |
| 28 Jan 2026 |
|  - changed their display name from Alexandru Tocar to -. | 18:34:44 |
| 1 Feb 2026 |
|  Fernando Rodrigues changed their display name from SigmaSquadron to Fernando Rodrigues. | 10:43:29 |
| 3 Feb 2026 |
|  zmitchell joined the room. | 17:23:16 |
| 9 Feb 2026 |
|  Brunouno joined the room. | 22:07:01 |
| 10 Feb 2026 |
|  Crony Akatsuki joined the room. | 21:33:44 |
| 12 Feb 2026 |
|  Adam joined the room. | 23:13:59 |
| 13 Feb 2026 |
|  hoplopf joined the room. | 10:26:33 |
| 17 Feb 2026 |
|  kasek joined the room. | 20:12:56 |
| 18 Feb 2026 |
|  tiferrei joined the room. | 20:16:58 |
| 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 |
