| 11 May 2022 |
 kamadorueda | I check-in the .envrc normally | 15:49:42 |
 a-kenji | This is something I am not sure about, I have checked it in until now too. | 15:49:57 |
 Vika (she/her) | In reply to @dpc:matrix.org
In a nixifified project using flakes, do you check-in the .envrc file into git, or is every contributor expected to create it if they use something like lorri? I check my .envrc into git personally | 21:38:39 |
| Vika (she/her) | That way a single direnv allow on a nix-enabled machine gets me my environment anywhere | 21:38:58 |
 dpc | So far I have been checking it in, but I wonder if it is ever undesireable or something. | 21:44:51 |
| a-kenji | The reason, I am not sure is: Maybe other people want to use it differently. | 21:54:02 |
| a-kenji | I usually am just adding use_flake, but other people might want a different .envrc. | 21:54:58 |
| 12 May 2022 |
| Vika (she/her) | In reply to @a-kenji:matrix.org
I usually am just adding use_flake, but other people might want a different .envrc. Why wouldn't you use a Nix-based environment if you have nix installed? I made my .envrc a no-op on systems that don't have nix in PATH, but for people who have it, they gonna get the same environment I use everywhere (if they choose to allow the .envrc to run) | 05:50:01 |
| Vika (she/her) | This is a sensible thing to do if you already have Nix on your machine | 05:50:33 |
| Vika (she/her) | ...with one caveat that flakes aren't gonna be enabled, but I think it might produce a somewhat helpful message if they aren't by means of nix rambling about experimental-optiona | 05:52:37 |
| Vika (she/her) | * ...with one caveat that flakes aren't gonna be enabled, but I think it might produce a somewhat helpful message if they aren't by means of nix rambling about experimental-options | 05:52:43 |
| a-kenji | In reply to @vika:fireburn.ru
Why wouldn't you use a Nix-based environment if you have nix installed? I made my .envrc a no-op on systems that don't have nix in PATH, but for people who have it, they gonna get the same environment I use everywhere (if they choose to allow the .envrc to run) Some people don't have flakes enabled, some might use a different invocation - with lorri / sorri / have their own nix-shell caching. This probably won't happen to many people, but every now and then I think about how this can be made a little bit more universal. | 08:29:17 |
| Vika (she/her) | In reply to @a-kenji:matrix.org
Some people don't have flakes enabled, some might use a different invocation - with lorri / sorri / have their own nix-shell caching. This probably won't happen to many people, but every now and then I think about how this can be made a little bit more universal. One could build detection for common workflows like lorri/sorri too. Having flakes disabled is also a valid concern, but once again, this could be potentially detected and handled | 08:30:38 |
| Vika (she/her) | flake-compat is a thing thankfully | 08:31:04 |
| a-kenji | In reply to @vika:fireburn.ru
One could build detection for common workflows like lorri/sorri too. Having flakes disabled is also a valid concern, but once again, this could be potentially detected and handled Yeah I need to look more into how to make it compatible with different use cases. | 13:18:56 |
| 13 May 2022 |
 oliver | Has anyone been able to install cargo-make (or other cargo components) via fenix? Or another toolchain provider? | 22:40:00 |
| 14 May 2022 |
| a-kenji | In reply to @oliver:matrix.nrp-nautilus.io
Has anyone been able to install cargo-make (or other cargo components) via fenix? Or another toolchain provider? Cargo make is a normal tool, that integrates with cargo and should be toolchain invariant. So you can just expose it inside of the devs hell. | 00:41:57 |
| a-kenji | * Cargo make is a normal tool, that integrates with cargo and should be toolchain invariant. So you can just expose it inside of the devshell. | 00:42:12 |
| oliver | That makes sense a-kenji . Do I have to explicitly link it to the fenix toolchain somehow? | 00:44:15 |
| a-kenji | No, you don't. As long as cargo and cargo make is in your shell path you can use it.
Here is an example with the oxalica overlay: https://github.com/zellij-org/zellij/blob/main/nix/default.nix#L86 , but I don't see a reason why it should be different with Fenix. | 00:48:07 |
| oliver | Thanks! | 01:00:03 |
|  Luke joined the room. | 02:49:31 |
| Luke | Is anyone here using Crane? I haven’t tried it, though it looks like a great tool. Further, I’m curious if it can handle maturin? I haven’t played around with PyO3 yet and would like to try it out for a project. | 03:17:50 |
| dpc | In reply to @luke:vuksta.com
Is anyone here using Crane? I haven’t tried it, though it looks like a great tool. Further, I’m curious if it can handle maturin? I haven’t played around with PyO3 yet and would like to try it out for a project. I just switched two little projects. | 03:32:05 |
| dpc | Before I was using flakes + naersk + fenix + lorri for everything. Now I swapped nearsk for crate. | 03:32:49 |
| dpc | Seems to work | 03:32:53 |
| dpc | Ability to define different passes with different arguments is nice. | 03:33:20 |
| dpc | * Ability to define different passes with different command/arguments is nice. | 03:33:33 |
| dpc | I never used maturin, but I would guess that crate only cares about running the right cargo command, rest is up to cargo. | 03:34:43 |
| Luke | In reply to @dpc:matrix.org
I never used maturin, but I would guess that crate only cares about running the right cargo command, rest is up to cargo. I’ll poke around at it - I’m not even really sure I need python bindings, it just seemed like the right idea to make this tool usable | 03:45:49 |
