| 19 Aug 2023 |
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 |