| 21 Apr 2025 |
 GGG | no problem! | 23:17:33 |
| GGG | I'm considering making a dotnet module to help people have a good .NET setup and avoid some of those pitfalls I mentioned (fixed env var, using runtime and sdk at the same time, etc.) | 23:18:11 |
 corruptcomputer | that would be fantastic if possible, something like environment.development.dotnet.enable = true; or similar would be so nice to have | 23:19:35 |
| GGG | I was thinking of something like programs.dotnet.enable = true and then you pick the versions you want and it'll configure env vars, files in /etc and stuff to make it work properly | 23:20:08 |
| GGG | then later on when MS finally figures out how they're gonna let distros package workloads it could tap onto that as well | 23:20:23 |
| corruptcomputer | Oh wait a minute, is it not possible to install the aspire workload with this? | 23:21:11 |
| corruptcomputer | I need that for my app to work... | 23:21:17 |
| GGG | since the directory where .NET lives is read-only, dotnet workload install doesn't work | 23:21:30 |
| GGG | I have no idea how to get workloads working with .NET in NixOS since I haven't used them myself | 23:21:44 |
| GGG | oh nevermind | 23:22:10 |
| GGG | apparently userlocal file instructs .NET to do the install per user | 23:22:23 |
| GGG | so it should be fine, my bad | 23:22:28 |
| corruptcomputer | Oh nice, ok thats good then | 23:22:35 |
| corruptcomputer | Yeah I am not super happy with the way workloads are handled, imo they should really be bundled with dotnet proper but I'm not MS so I can't change that :/ | 23:23:14 |
| corruptcomputer | I've had so many issues with updating dotnet, forgetting to update the workloads, and the app just failing every build until I remembered to do that | 23:23:32 |
| GGG | having optional components is good to keep size and dependencies down, but it's annoying how they have their own package management solution instead of delegating it to distros | 23:23:54 |
| GGG | they seem to have plans to let distros package them, but I don't know at which stage that is at right now | 23:24:11 |
 6pak | or just making them regular project deps | 23:24:22 |
| 6pak | but keep in mind you have to do it yourself | 23:24:31 |
| 6pak | in your nixos config | 23:24:36 |
| 6pak | another thing a nixos module could handle | 23:24:44 |
| GGG | do what in your nixos config exactly? | 23:24:54 |
| GGG | I think corngood changed the SDK to have that file by default iirc | 23:25:07 |
| 6pak | oh | 23:25:12 |
| 6pak | the source built ones might have them sure | 23:25:16 |
| 6pak | I use the binary sdks | 23:25:20 |
| GGG | oh, the binary ones don't? we should change the install script to fix that | 23:25:38 |
| 6pak | actually I don't see the userlocal file in source built sdks either? | 23:27:03 |
| 6pak | oh, only 1xx feature band is source built, right | 23:27:47 |
| corruptcomputer | So out of curiosity, if I were wanting to try to contribute to NixOS, how would I do that? I've never contributed to a distro before, but NixOS to me seems like it might be a good place to start since everything is defined as code so I'm hoping it'll be a lot more familiar to me as a developer than other distros are | 23:28:10 |
