| 25 Feb 2025 |
 raitobezarius | In reply to @acidbong:envs.net
evening, fellers and felines, i'm back with my CI struggles
this Sunday I updated nixpkgs, and Lix (i'm backporting a patch) failed to build in CI (Codeberg's Woodpecker), but it built successfully on my PC. what could be the reason?
latest successful log: https://ci.codeberg.org/repos/14075/pipeline/19/9
the failed one: https://ci.codeberg.org/repos/14075/pipeline/34/6 looks flakey, did you try again? | 00:06:01 |
|  Leg O'Worm changed their profile picture. | 01:33:22 |
 Acid Bong | @raitobezarius:matrix.org i did, pipeline 34 is the restarted 32 (which also failed the same way), click on the repo name to see them
and on the third try (pipeline 35: I just changed pkgs/default.nix, but not radically) instead of failing another test just timed out (Codeberg's Woodpecker runner is really slow) | 05:29:34 |
|  Kücki Eben left the room. | 09:06:50 |
|  @neolumine:matrix.org left the room. | 14:29:27 |
 Charles | how bad is the concept of NIX_PATH really? | 19:43:14 |
| raitobezarius | It's just an environmental impurity but it doesn't shock me | 20:01:29 |
 Arian | ive put
NIX_PATH=nixpkgs=https://channels.nixos.org/<exact-tarball-here>
in .envrc before as a quick way to share a locked nixpkgs in repos
| 20:02:58 |
 Lily Foster | what about how order of stuff in NIX_PATH can be signficant depending on names | 20:03:26 |
 validitymaiden | When using Lix in NixOS by way of /etc/nixos/configuration.nix, is specifying a version of Lix necessary? Is there a way to just use whatever is current? | 20:04:01 |
 K900 | nix.package = pkgs.lix will give you usually latest | 20:05:15 |
 just1602 | In reply to @validitymaiden:matrix.org
When using Lix in NixOS by way of /etc/nixos/configuration.nix, is specifying a version of Lix necessary? Is there a way to just use whatever is current? If you want to use the module you need to specify the version because there's still work to do to have a stable branch or tag always pointing to the latest stable version | 20:06:26 |
 522 | wait, what's the stable branch for then? | 20:08:32 |
| validitymaiden | that worked much easier, thank you 💜 | 20:12:49 |
| just1602 | From what I see on git.lix.systems, there's no stable branch | 20:59:19 |
| 522 | https://git.lix.systems/lix-project/nixos-module/src/branch/stable | 20:59:43 |
| 522 | for the module there is | 20:59:47 |
| just1602 | Oh don't know, maybe it was added ! :o | 21:07:19 |
 KFears (no longer human) | In reply to @charles:computer.surgery
how bad is the concept of NIX_PATH really? The concept? I think it's alright, though not optimal and somewhat outdated. I'd much rather have a hardcoded default entrypoint that can be overridden with args. Env vars are a lot less controllable and granular | 22:37:38 |
| Charles | Another problem is that it's annoying to bootstrap if your config sets it and also depends on it | 22:43:12 |
| KFears (no longer human) | Yes, very very much | 23:16:19 |
| KFears (no longer human) | I think the lesson to be learned is that /bin/sh-style of approach is good and working | 23:17:17 |
| KFears (no longer human) | You use one hardcoded, well-known location, and then you solve for cased when you desire anything else | 23:18:08 |
| KFears (no longer human) | NIX_PATH is more similar to Bash impurity | 23:18:23 |
| 26 Feb 2025 |
|  Michal Koutenský joined the room. | 00:00:27 |
 crop | In reply to @r522:matrix.org
https://git.lix.systems/lix-project/nixos-module/src/branch/stable Using the module in your configuration makes sense so that tools depending on nix also use lix. The shortcut k900 mentioned is to use lix from nixpkgs. Which also makes sense to me as a user. I use the module with nixpkgs lix. If one wants to use lix releases from source then one needs to change the branch for every release (currently). | 00:10:58 |
| Charles | it's sad that formal arguments (i.e. { foo, bar, ...}: ... syntax) can't use arbitrary strings as argument names | 00:33:43 |
| Charles | okay i made https://gitlab.computer.surgery/charles/sprinkles/-/issues/1 about pros/cons between NIX_PATH and formal arguments and i think the latter is the better option | 01:26:00 |
| raitobezarius | In reply to @charles:computer.surgery
okay i made https://gitlab.computer.surgery/charles/sprinkles/-/issues/1 about pros/cons between NIX_PATH and formal arguments and i think the latter is the better option I don't agree with the cons of option 1 | 01:56:09 |
| raitobezarius | Manipulating NIX_PATH in local shells is an option | 01:56:31 |
