Nix + dotnet | 116 Members | |
| 24 Servers |
| Sender | Message | Time |
|---|---|---|
| 24 Oct 2025 | ||
Sorry, that sounded sarcastic, I meant it seriously 😅 and thanks for your help so far | 13:41:53 | |
| Can I point the fetch-deps to a custom nuget server for some packages? Or at least pass it a NuGet.config that has the custom server configured? | 13:46:14 | |
Ohh. I think if I name it properly (nuget.config instead of NuGet.config) it detects it automatically. | 13:53:13 | |
| Did you get a complete deps.json then? | 14:09:51 | |
| 27 Oct 2025 | ||
No, the fetcher failed and didn't create a deps.json. I'll try again soon when I get the complete closed source dependencies from our partner | 08:32:51 | |
| 2 Nov 2025 | ||
| question, how do i use the fetchdeps thing with the nix cli? | 19:31:00 | |
| doing a | 19:31:45 | |
In reply to @emma:rory.gayYou can't use .# because that'll be a read-only copy. Try -f . instead | 19:33:03 | |
| oh apparently you can just pass a path... lol | 19:33:05 | |
| that fails because i dont have a default.nix... lol | 19:33:38 | |
| You can pass a .nix file path instead of . | 19:34:14 | |
| i have a flake.nix | 19:34:26 | |
| thats the only .nix file i have | 19:34:29 | |
| (i dont want to maintain 6 identical copies of the same file when they only differ in at most 2 lines) | 19:35:22 | |
| Oh, you can also pass a path to fetch-deps itself to override it. That might be easiest | 19:35:27 | |
| yep discovered that one already | 19:35:38 | |
| but i guess that's my best bet | 19:35:44 | |
| Yeah otherwise you need to do an impure eval, maybe using flake compat or something. Passing the path is probably easiest. | 19:37:12 | |
| hm, i wonder what the best way would be to use nix to publish nuget packages | 19:53:00 | |
since packNupkg emits multiple nupkg files, im not sure how ot best deal with thta | 19:53:31 | |
also wondering how to best handle versioning, since my current ci setup uses current time for that | 19:58:31 | |
that's my current ci setup, that i'd like to get rid of | 19:59:17 | |
| 20:09:36 | ||
| oh... i didnt realise but the nupkg files are empty... lol | 21:17:21 | |
| 3 Nov 2025 | ||
| Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
| 18:03:55 | |
| * Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
EDITING | 18:04:02 | |
| * Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
| 18:06:10 | |
A basic question. The .nupkg file with the dlls that should do all the heavy lifting: Should I make a proper package out of it with buildDotnetModule, stdenv.mkDerivation or similar, and pass it to my wrapper project as buildInputs? Or is that not necessary because the dlls are on the nupkg server and should be autodetected through deps.json? | 18:09:42 | |
| * Still trying to package my wonky project. I got a new version of the dll dependencies my partner's nuget server, and a wrapper project that depends on it as source code. I'm puzzled how to set projectFile.
EDIT: Nevermind 2. & 3., it seems that | 18:15:30 | |
not necessary, it'll be detected through deps.json | 20:31:40 | |