Nix + dotnet | 128 Members | |
| 24 Servers |
| Sender | Message | Time |
|---|---|---|
| 25 Dec 2024 | ||
| No idea, I got them a while ago from another config and never got around to checking if/why they're needed | 20:57:17 | |
| Was easy enough to keep around so I just did | 20:57:25 | |
| looks like something that could break global.json sdk version selection logic | 20:58:10 | |
| I generally dislike `global.json` and get rid of it whenever I see it so it's fine to me | 21:13:47 | |
| 26 Dec 2024 | ||
| 01:41:20 | ||
| 01:42:03 | ||
| Thank you, but unfortunately that didn't help. I always get the standard error message: Could not start dynamically linked executable: ./Hygrometer.InfluxDB.Collector NixOS cannot run dynamically linked executables intended for generic linux environments out of the box. For more information, see: https://nix.dev/permalink/stub-ld | 10:48:09 | |
| 1 Jan 2025 | ||
| Hey gang, is there a suggested way to migrate a This is mainly in reference to the header(?) comments from a
| 01:05:55 | |
In reply to @whovian9369:matrix.orgUse touch deps.json, change nugetDeps to point to that and then run fetch-deps | 01:09:49 | |
Ah, so fetch-deps is basically looking for a different extension? I'll do so soon then, thank you! | 01:10:29 | |
| Yeah, we changed it to generate JSON files because the new standard in nixpkgs is to not generate code for data | 01:10:55 | |
| It still works with nix files, but it's mainly for compatibility sake | 01:11:10 | |
| Any other file extensions it generates JSON | 01:11:24 | |
| I liked being able to read the deps files as Nix because it's all the same ecosystem, but that makes perfect sense. Thanks! | 01:11:39 | |
| Well, the JSON file isn't *that* different | 01:14:49 | |
| It's just the arguments to `fetchNuGet` | 01:15:01 | |
| Hah, fair | 02:08:47 | |
| Now comes the painful part of changing all of my dotnet self-packages, haha | 02:13:24 | |
| 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 | |
In reply to @whovian9369:matrix.orgIt's not actually causing you any immediate problem, is it? deps.nix should still work, including with fetch-deps. | 02:23:21 | |
| I don't use a Nixpkgs fork for my self-packages, but I appreciate it! Thank you! | 02:24:09 | |
In reply to @whovian9369:matrix.orgOh 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 | |
| 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 | |
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 | |
| That's interesting, thank you! | 02:29:22 | |
In reply to @gggkiller:matrix.org 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? | 12:20:33 | |
| 14:26:34 | ||
I believe you would just do > deps.json instead. | 15:40:52 | |
Is there a realistic solution to avoiding this issue when trying to build the deps file? | 15:42:11 | |
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 | |