| 7 May 2025 |
 dramforever | if you have your own package set you can also easily use it from the cli | 12:21:19 |
| dramforever | i don't know if you're going that far yet | 12:21:25 |
 paintenzero | Ah, I see now. That makes sense. Thank you! | 12:22:23 |
 Sandro 🐧 | yep. registry is no longer used for that because it depends on user configuration | 12:36:57 |
| Sandro 🐧 | managing channels is no fun when you have more than 2 and especially painful when you have 10+ | 12:37:23 |
| Sandro 🐧 | Flakes are the defacto standard. You can use something else but that is usually gefrickel and may not be supported by everything. | 12:37:47 |
| paintenzero | And by managing channels you mean managing compatibility between all the software from different channels? | 12:47:36 |
| Sandro 🐧 | creating, deleting them, pointing them to the correct branch | 12:48:17 |
| Sandro 🐧 | rolling them back | 12:48:22 |
| paintenzero | Understood. Thank you! | 12:49:23 |
 Mr. Defenestrator | In reply to @sandro:supersandro.de
yep. registry is no longer used for that because it depends on user configuration Interesting. So I can't use system registry references for nix eval? It works for 'global' references. Is there an issue I can go read into? | 13:38:47 |
| Sandro 🐧 | It was mentioned in the changelog of nix 2.28 IIRC | 13:42:57 |
| Sandro 🐧 | nix eval should still work, just not putting it directly into flake.nix | 13:43:17 |
| Mr. Defenestrator | Actually I found a few upstream issues, it looks like this may be a bug. See https://github.com/NixOS/nix/issues/13144
Reading into it, can't really discern if this was an intended effect of the pinning change or unintended. | 13:51:25 |
| Mr. Defenestrator | Hopefully it's just a regression, that syntax with a 'self' flakeref in the registry is super ergonomic for auto updates among other things. | 13:53:09 |
| Mr. Defenestrator | * Actually I found a few issues, it looks like this may be a bug. See https://github.com/NixOS/nix/issues/13144
Reading into it, can't really discern if this was an intended effect of the pinning change or unintended. | 13:57:15 |
|  @wimpress:matrix.org changed their profile picture. | 15:12:16 |
|  Ethan joined the room. | 16:10:33 |
 hexa | what is a good output to run nixos vm tests in | 20:57:46 |
| hexa | we have a bunch of them, like 10 | 20:57:51 |
| hexa | so I want them out of checks, because they make nix flake check too expensive | 20:58:11 |
| hexa | but ideally I could just nix build .#tests | 20:58:26 |
| hexa | without having to select an individual test | 20:58:37 |
|  @skyesoss:matrix.org left the room. | 20:58:40 |
| hexa | but with the option to | 20:58:41 |
| hexa | but e.g. package attributes can only be derivations or paths | 20:59:37 |
| Sandro 🐧 | create a dummy derivation tests which just draws in everything | 21:26:36 |
|  christopherg98 joined the room. | 22:33:07 |
| 8 May 2025 |
| Mr. Defenestrator | It'd be cool if --argstr worked with flake checks. I just did a little test and it failed because my arg wasn't defined in _module.args -- I didn't think checks relied in the module system, but that's kind of interesting if they do.
Maybe someone who knows more about the checks attribute could confirm that. Parameterizing checks could be useful. | 04:36:15 |
| dramforever | flake checks don't inherently use the module system as they're just derivations. do you use something like flake-parts? | 07:29:57 |
