| 19 Aug 2023 |
 Emma [it/its] | im guessing the dotnet packages also cant be extended to ship with the workloads builtin? | 11:50:54 |
 mdarocha | there were attempts from what i remember, see the issue i linked above | 11:51:33 |
| mdarocha | but properly implementing workloads in nix would require understanding how they are installed by the dotnet cli so that we can provide them using the standard nix functions | 11:52:14 |
| Emma [it/its] | at least going by https://github.com/NixOS/nixpkgs/blob/nixos-23.05/pkgs/development/compilers/dotnet/versions/7.0.nix, there seems to be a packages array, couldnt the missing ones be added there? | 11:52:19 |
| mdarocha | nope, this package array is used to streamline the package updating process | 11:53:07 |
| Emma [it/its] | it looks like theyre all just installed to /usr/share/dotnet/packs | 11:53:16 |
| Emma [it/its] | * it looks like theyre all just installed to /usr/share/dotnet/packs (arch) | 11:53:21 |
| mdarocha | ie those package are implicitly included with every does, and thanks to that we don’t have to regenerate all the deps.nix in the nixpkgs tree | 11:53:43 |
| mdarocha | if you want to take a stab at implementing workloads then PRs are welcome :) I unfortunately didn’t have the time to take a look at that issue | 11:54:13 |
| Emma [it/its] | both eg. Microsoft.AspNetCore.App.Ref and Microsoft.NETCore.App.Runtime.Mono.browser-wasm appear to be in in that same /usr/share/dotnet/packs directory | 11:54:34 |
| mdarocha | * ie those package are implicitly included with every deps, and thanks to that we don’t have to regenerate all the deps.nix in the nixpkgs tree | 11:54:41 |
| Emma [it/its] | In reply to @magikarpz:matrix.org
if you want to take a stab at implementing workloads then PRs are welcome :) I unfortunately didn’t have the time to take a look at that issue i'd try but i have close to no experience with nix as a language, so i'd have no idea about actually implementing anything | 11:55:45 |
| Emma [it/its] | i'd be willing to test manually add all the workload packages into packages in 7.0.nix but i'd need to figure out how i'd even calculate all the sha256's | 11:57:58 |
| mdarocha | you can start by looking into dotnet’s update.sh script to see how they are generated | 11:58:35 |
| mdarocha | but for workloads, I believe a better starting point will be the nix-maui rep referenced in the issue I linked | 11:59:02 |
| Emma [it/its] | well there the issue starts that i have no clue what i'm doing when it comes to nix | 11:59:34 |
| mdarocha | yeah, this unfortunately doesn’t seem like an easy issue for beginners :/ | 12:00:03 |
| Emma [it/its] | hence why i proposed to test if adding all workloads' packages into the packages array would work in a local nixpkgs checkout | 12:00:41 |
| Emma [it/its] | though, it looks like i could just add the package names in update.sh and the script would take care of the hashes? | 12:01:24 |
| mdarocha | you can check it, sure, I’m not sure if it will work or not | 12:01:25 |
| mdarocha | yep, that’s how the lost in the nix files is generated | 12:01:40 |
| mdarocha | * yep, that’s how the list in the nix files is generated | 12:01:47 |
| Emma [it/its] | i wish i had the bandwidth to just clone the repo in full without --depth=1 | 12:03:30 |
| Emma [it/its] | oh well | 12:03:35 |
| Emma [it/its] | the nix maui flake does seem to have all of the workloads written down in nix | 12:12:52 |
| Emma [it/its] | oh, you can just use nix-prefetch-url to get the hash, neat | 12:17:05 |
| 23 Aug 2023 |
|  witchof0x20 left the room. | 05:58:09 |
| 5 Sep 2023 |
|  Rover left the room. | 13:50:12 |
| mdarocha | can somebody with merge access take a look at this? https://github.com/NixOS/nixpkgs/pull/248208 | 16:57:27 |
| 21 Sep 2023 |
|  dedmunwalk joined the room. | 23:06:38 |
