| 21 Apr 2025 |
 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 |
| 6pak | Redacted or Malformed Event | 23:28:17 |
| GGG | yeah, only it is built | 23:28:28 |
| corruptcomputer | I've briefly looked into contributing to fedora before, but it seemed so over the top complicated that I just gave up before I even started | 23:28:35 |
| GGG | also, things might have changed. I'm not finding anything with nix-locate | 23:28:44 |
| 6pak |
Message deleted by NixOS Moderation Bot
wha
| 23:28:45 |
| 6pak | /tmp
❯ nix build p#dotnetCorePackages.sdk_9_0_1xx && ls -R ./result/share/dotnet/metadata/workloads/
9.0.100
./result/share/dotnet/metadata/workloads/9.0.100:
userlocal
/tmp
❯ nix build p#dotnetCorePackages.sdk_9_0_1xx-bin && ls -R ./result/share/dotnet/metadata/workloads/
"./result/share/dotnet/metadata/workloads/": No such file or directory (os error 2)
[ble: exit 2]
| 23:29:02 |
| GGG | oh yeah, with the whole illegal image spam fiasco in the main NixOS room, image uploading got restricted | 23:29:10 |
| GGG | basically find what you want to change in the nixpkgs monorepo, make the changes you want, commit into a new branch, run nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" and then run the programs to see if they still work | 23:32:15 |
| GGG | but .NET is more annoying than usual because if you change something in the SDKs, they'll cause every .NET program in nixpkgs to also be rebuilt, so you'll spend quite a few hours on the rebuild | 23:32:49 |
| GGG | I recommend reading parts of the nixpkgs manual first, so you learn how things work in nix, since it's quite different from any other distro | 23:33:20 |
| GGG | * basically find what you want to change in the nixpkgs monorepo, make the changes you want, commit into a new branch, run nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD" and then run the programs to see if they still work and make a PR back to the main repo | 23:33:50 |
| corruptcomputer | Just to be sure, is this the manual you mean?
https://nixos.org/manual/nixpkgs/stable/index.html | 23:34:21 |
