| 15 Oct 2025 |
 raitobezarius | but that's nix2 realm | 01:28:37 |
| raitobezarius | so I defer to nix2 expert, piegames | 01:28:42 |
| raitobezarius | as far as I'm concerned, I feel the builtin path for this seems unlikely | 01:29:19 |
 Charles | i agree | 01:29:33 |
| raitobezarius | In the current constraints of Nix1, linting is the best available option perhaps | 01:29:40 |
| raitobezarius | (or scopedImport as you said but separate file) | 01:29:49 |
| Charles | (which would be the case that fails eval because source is not nameable here) | 01:30:17 |
| Charles | i think you transposed these two things but yeah | 01:30:46 |
| raitobezarius | sorry ^^, 3am | 01:30:57 |
| Charles | np lol | 01:31:05 |
 piegames | Nyaaaaawn | 05:46:49 |
| * piegames backlogs | 05:46:54 |
| piegames | Whatever you do, it needs to fail at parse time nit run time | 05:52:44 |
| piegames | I think a specially scoped closure à la Rust moving semantics would be possible in theory | 05:53:08 |
| piegames | But also, I think that we should probably look into module systems first to see if they can solve that better | 05:53:39 |
 eyJhb | Minor thing raitobezarius , but the ! at the end of the link in #announcements:lix.systems gets interpreted as part of the link in some clients :D | 05:58:38 |
| Charles | i would guess a module system would fulfill this desire, yeah | 06:04:16 |
 KFears (burnt out) | Is there anything that improves modules planned, btw? | 06:14:07 |
| Charles | In reply to @kfears:matrix.org
Is there anything that improves modules planned, btw? This is modules as in programming language module systems, not as in nixos modules | 06:18:38 |
| KFears (burnt out) | Ah
Well, anything for NixOS modules, as a treat? :) | 06:21:37 |
|  MrWildBunnycat joined the room. | 14:54:40 |
|  ellyse_e joined the room. | 17:10:09 |
 antifuchs | inspired by a conversation earlier, I got a f attribute on my lix repl now that loads the flake in the current directory, but using flake-compat (and searching upwards for a flake.nix). took a looong time, but yay (also, I guess the best thing about this is the realization that I could import nixpkgs/lib as a lib repl attribute too) | 23:00:58 |
| 16 Oct 2025 |
 somasis | sorry if this is too off topic, but i've been wondering lately (especially since the flakes feature freeze stuff was posted): do people have suggestions of best practices for organizing nixos configs without using flakes, involving niv, npins, or lon, or whatever? I started using nixos using flakes, but i'm interested in reorganizing my config to work without flakes now (ideally without channels ever being involved) | 01:51:58 |
 ekler | i find npins to be okay, it's also easy to use
| 02:21:41 |
| ekler | just note that there's two things called "channels": the things on channels.nixos.org (and you can manage references to those with npins which allows proper locking) vs the stuff on your local system that is managed via nix-channel + NIX_PATH (which is the impure, messy stuff that you don't want)
| 02:23:28 |
| somasis | indeed | 02:28:41 |
| somasis | I think one of the things that trips me up with flakes vs. non flakes is how nixos-rebuild finds the host you're trying to build, compared to when it's expecting a non-flake configuration; it seems like you're not expected to have multiple hosts in one configuration directory in non-flakes style, yet you are with flakes. so it makes me wonder if there's practices people have came up with for maintaining some of the nice stuff about flake-oriented configuration style without relying on flakes | 02:31:07 |
| ekler | i would still use the hosts/*.nix setup, where each file is an entry-point for a respective host, and use -I nixos-config=hosts/thishost.nix or whatnot
| 02:34:03 |
| ekler | obv that's not the only way to do it, but it works for me
| 02:34:19 |
