| 13 May 2024 |
 @tc424:glasgow.social | In reply to @tc424:glasgow.social
Oh https://github.com/brianmcgee/nvix Linked from https://bmcgee.ie/posts/2023/10/nvix-implementing-a-tvix-store-with-nats/ | 20:20:49 |
 MangoIV | In reply to @delroth:delroth.net
the flakes implementation in Lix is arguably more stable than Nix, who broke several user-facing APIs completely through bugs in the past 2-3 versions That’s partially why I was asking, but no answer is good enough as an answer for me now then. I’ll keep watching :) | 20:53:03 |
|  Triskelion (AFK) changed their display name from Triskelion to Triskelion (AFK). | 21:26:26 |
 samrose | In reply to @tc424:glasgow.social
Linked from https://bmcgee.ie/posts/2023/10/nvix-implementing-a-tvix-store-with-nats/ This looks pretty amazing ... | 21:30:20 |
|  quentin joined the room. | 21:56:14 |
|  easrng joined the room. | 22:38:44 |
| easrng | i just rebuilt with nix.package = pkgs.lix now that it's in nixpkgs and everything seems to work, is there any reason not to do this? | 22:43:16 |
 puck | The version of Lix in nixpkgs will likely lag behind by a bit; and the dedicated overlay/module will build other packages that depend on Nix with Lix as well; which doesn't happen in nixpkgs. | 22:45:37 |
| easrng changed their profile picture. | 22:46:02 |
 mjm | In reply to @easrng:yuri.im
i just rebuilt with nix.package = pkgs.lix now that it's in nixpkgs and everything seems to work, is there any reason not to do this? this is what i'm doing too | 22:46:34 |
| samrose | In reply to @puck:puck.moe
The version of Lix in nixpkgs will likely lag behind by a bit; and the dedicated overlay/module will build other packages that depend on Nix with Lix as well; which doesn't happen in nixpkgs. If we nix build on the flake in the source repo this overlay/module and the packages it builds will be part of the build then, is that right? | 23:08:40 |
 @fly:asra.gr | In reply to @puck:puck.moe
The version of Lix in nixpkgs will likely lag behind by a bit; and the dedicated overlay/module will build other packages that depend on Nix with Lix as well; which doesn't happen in nixpkgs. mew, did you figure out why it builds electron with our nixpkgs version? | 23:09:33 |
 Qyriad | ugh this is that issue where they somehow got Nix in Electron's closure. did they not backport the fix for that to older Nixpkgs? | 23:10:15 |
| Qyriad | In reply to @samrose:matrix.org
If we nix build on the flake in the source repo this overlay/module and the packages it builds will be part of the build then, is that right? I'm not sure I understand you correctly, but I don't think so — the flake in the lix-project/lix repo is not actually exactly the same derivation as the one the overlay exports | 23:11:13 |
| samrose | In reply to @samrose:matrix.org
If we nix build on the flake in the source repo this overlay/module and the packages it builds will be part of the build then, is that right? I guess we can also use the installer on a fresh machine. I hadn’t even dug into trying to install Nixos using Lix or maybe not yet possible? | 23:11:52 |
| samrose | In reply to @qyriad:katesiria.org
I'm not sure I understand you correctly, but I don't think so — the flake in the lix-project/lix repo is not actually exactly the same derivation as the one the overlay exports Ok thanks | 23:12:43 |
| Qyriad | In reply to @samrose:matrix.org
I guess we can also use the installer on a fresh machine. I hadn’t even dug into trying to install Nixos using Lix or maybe not yet possible? the NixOS installer doesn't have like, an option to select Lix instead (yet 🙂), but you could probably hack the installer to use a specific overlay or something. or you could just switch after installation 🤷she | 23:13:40 |
|  DarkKronicle joined the room. | 23:17:11 |
| samrose | In reply to @qyriad:katesiria.org
I'm not sure I understand you correctly, but I don't think so — the flake in the lix-project/lix repo is not actually exactly the same derivation as the one the overlay exports Sorry for my being confusing. I was thinking about cases where I am using nix on non-nixos systems (crazy, I know), but realized the discussion about the module/overlay might be in the context of installing Lix in nixos? | 23:18:03 |
| samrose | (I use nixos for some projects, but also have many cases where I just use nix on other linux distros. I was experimenting with using Lix on non-nixos contexts.) | 23:20:20 |
| Qyriad | ahhh oops | 23:25:06 |
| Qyriad | the module is specific to NixOS, though you can use the overlay it exports from non-NixOS | 23:25:26 |
| Qyriad | but in general you can just use the lix installer on non-NixOS | 23:25:39 |
 DolceTriade | Can you have nix and Lix installed together or will they fight over the "nix" binary? | 23:30:12 |
| Qyriad | you'll just end up with two nixs in your path, depending on how you install. the bigger thing is that only one daemon will be in use, which is not a huge problem since right now they are compatible, but we wouldn't recommend having two Nix implementations installed at once unless you have a good reason to | 23:31:26 |
| samrose | In reply to @qyriad:katesiria.org
but in general you can just use the lix installer on non-NixOS I feel like many people might have the opinion that you'd be kinda crazy not to just use Nixos, and I actually agree. But I have some reasons to use just nix in some cases. And, I also don't mind testing, and even trying to help fix the non-nixos use cases in Lix too. I also do use flake registries, and nix profile install in some non-nixos cases (and it actually works surprisingly well). I can't foresee a reason to have nix and lix together on the same system. | 23:36:42 |
| Qyriad | there are plenty of reasons to use Nix on non-NixOS systems tbh | 23:41:07 |
| Qyriad | we very much support that use case | 23:41:13 |
| Qyriad | * there are plenty of reasons to use Nix on non-NixOS (Linux) systems tbh | 23:41:20 |
| Qyriad | it is, admittedly, less tested, but only because it's much harder to do testing for it | 23:41:36 |
