| 1 Jan 2025 |
 GGG | There's the script I wrote to do the treewide change in nixpkgs if you want: https://gist.github.com/GGG-KILLER/3a52e6244bbd14dd38e27f115e0ad2d6 | 02:22:12 |
 Corngood | In reply to @whovian9369:matrix.org
Now comes the painful part of changing all of my dotnet self-packages, haha It's not actually causing you any immediate problem, is it? deps.nix should still work, including with fetch-deps. | 02:23:21 |
 Whovian9369 | I don't use a Nixpkgs fork for my self-packages, but I appreciate it! Thank you! | 02:24:09 |
| GGG | In reply to @whovian9369:matrix.org
I don't use a Nixpkgs fork for my self-packages, but I appreciate it! Thank you! Oh no, you can run this in your repo and it'll migrate everything it can, it's not something that works only in nixpkgs | 02:24:42 |
| GGG | I haven't tested outside of nixpkgs but it *should* work on any nix file as long as it can find `nugetDeps = ...` | 02:25:42 |
| Whovian9369 | It's not, but it's just tedious as hell considering $ fd --type=f deps | wc -l says that I have 31 files -- Subtract a few (like the deps.json that I have for a Ghidra plugin or my "backup" deps.nix files that I never got around to deleting) and it's not an insignificant amount of work 😅 | 02:29:13 |
| Whovian9369 | That's interesting, thank you! | 02:29:22 |
 Daniel | In reply to @gggkiller:matrix.org
There's the script I wrote to do the treewide change in nixpkgs if you want: https://gist.github.com/GGG-KILLER/3a52e6244bbd14dd38e27f115e0ad2d6 Unfortunately, the script only works with experimental Nix feature 'nix-command' ... Until now I have always created my deps as follows, is there also a tool for json?
nuget-to-nix $HOME/nuget_pkgs > deps.nix | 12:20:33 |
|  NixOS Moderation Botchanged room power levels. | 14:26:34 |
| Whovian9369 | I believe you would just do > deps.json instead. | 15:40:52 |
| Whovian9369 | $ nix build -L .#ndecrypt-git
warning: Git tree '/home/whovian/.flakes/nix-game-preservation' is dirty
error:
… while evaluating an expression to select 'drvPath' on it
at «internal»:1:552:
… while calling the 'derivationStrict' builtin
at «internal»:1:208:
(stack trace truncated; use '--show-trace' to show the full trace)
error: syntax error, unexpected end of file, expecting expression
at /nix/store/qg2pdhwccz82apli9d6kc4r7agp04bza-source/ndecrypt/deps-git.json:1:1:
Is there a realistic solution to avoiding this issue when trying to build the deps file?
| 15:42:11 |
| Whovian9369 | The issue's come up quite often for me with deps.nix but now it's appearing with deps.json for me as well, which is a bit frustrating for likely obvious reasons. | 15:42:46 |
| Whovian9369 | So it looks like the answer is to fill in src.hash first, or work around it by doing nix build -L .#ndecrypt-git.src (for example) first. | 15:56:51 |
| Corngood | Isn't it `nuget-to-json` now? | 16:04:27 |
| Whovian9369 | Right, nice catch. | 16:04:56 |
| Whovian9369 | * I believe you would just do nuget-to-json $HOME/nuget_pkgs > deps.json instead. | 16:05:12 |
| Whovian9369 | Edited my above message | 16:05:18 |
 Emmanuel Genga | Does fetch-deps still work the same if I set the output file to deps.json? | 19:39:33 |
| Corngood | In reply to @genga898:matrix.org
Does fetch-deps still work the same if I set the output file to deps.json? Yeah, it should do | 19:43:08 |
| 2 Jan 2025 |
|  Vera left the room. | 11:48:08 |
| 9 Jan 2025 |
| GGG | 
Download image.png | 13:01:47 |
| GGG | 6pak: got back to looking at patchcil and I found where it lists the paths for native dependencies: | 13:01:49 |
| GGG | * 6pak: got back to looking at patchcil and I found where it lists the paths for native dependencies | 13:01:52 |
| GGG | but it seems like after the build, it just copies them to the root | 13:02:42 |
| GGG | 
Download image.png | 13:02:44 |
| GGG | so I don't know if we really need to read .deps.json or not, but I guess I'll implement it regardless | 13:03:15 |
| GGG | seems like no packages have the runtime/{rid} in their output either: | 13:12:36 |
| GGG | 
Download image.png | 13:12:39 |
 6pak | I forgot it will get flatten out when building for a specific RID, yeah | 15:49:48 |
| 6pak | what does the deps.json point to in that case? | 15:49:57 |
