Nix + dotnet | 126 Members | |
| 24 Servers |
| Sender | Message | Time |
|---|---|---|
| 4 Dec 2024 | ||
I originally had it in mind to remove the top level aliases, but now I'm not so sure. I added dotnet-sdk_9 recently to be consistent with the other versions. | 19:25:05 | |
Download image.png | 19:28:09 | |
| There's a bit more of confusion: there's no dotnet-aspnetcore_8 | 19:28:20 | |
There is, but dotnet-aspnetcore is an alias for it | 19:28:54 | |
| What's that from? Maybe we can clean up what's being reported a bit | 19:29:26 | |
| https://search.nixos.org/packages?channel=24.11&from=0&size=50&sort=relevance&type=packages&query=dotnet-aspnetcore | 19:29:35 | |
| This is what I'm currently using as a app/package store for NixOS | 19:29:57 | |
| really not the best thing for it, does anyone know anything better? | 19:30:21 | |
I'm sorry, this is wrong. dotnetCorePackages.dotnet_9.sdk is the source-built sdk, and dotnet-sdk_9 is the binary SDK. | 19:31:34 | |
dotnet-sdk_9 is an alias of dotnetCorePackages.sdk_9_0 | 19:31:49 | |
| should one care? | 19:31:59 | |
| Not really. At some point I'd like to make the top level aliases point at the source-built versions. Once they build reliably on all platforms. | 19:32:59 | |
| * +nothing. they're the same package+ | 19:33:40 | |
| * ~~nothing. they're the same package~~ | 19:34:00 | |
| * | 19:34:40 | |
| Still getting confused I have the following two system packages installed + Rider: dotnetCorePackages.dotnet_8.aspnetcore dotnet-sdk_9 and yet I get $ dotnet --info Host: Version: 8.0.11 Architecture: x64 Commit: 9cb3b725e3 RID: linux-x64 .NET SDKs installed: No SDKs were found. .NET runtimes installed: Microsoft.AspNetCore.App 8.0.11 [/nix/store/pyh7d87igawxpr9qnpc0ap4v0irx3591-dotnet-aspnetcore-runtime-8.0.11/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 8.0.11 [/nix/store/pyh7d87igawxpr9qnpc0ap4v0irx3591-dotnet-aspnetcore-runtime-8.0.11/share/dotnet/shared/Microsoft.NETCore.App] Other architectures found: None Environment variables: Not set global.json file: Not found Learn more: https://aka.ms/dotnet/info Download .NET: https://aka.ms/dotnet/download $ which dotnet /run/current-system/sw/bin/dotnet | 19:56:41 | |
| Check this out: https://nixos.org/manual/nixpkgs/stable/#using-many-sdks-in-a-workflow You need to combine them into a single package because the | 20:18:12 | |
| What about global environment? | 20:19:12 | |
you can install the output of combinePackages wherever you're using e.g. dotnet-sdk_9 | 20:19:58 | |
| 21:44:23 | ||
| 21:52:55 | ||
| 5 Dec 2024 | ||
| 12:51:19 | ||
| 18:43:11 | ||
| A question about Rider and FHS environments: Rider is sort of single instance app, e.g. all windows are actually run by a single instance of Rider. How do you deal with that and the need for FHS environments? Do I even need FHS environments? Could I make Rider somehow use nix tooling for building packages? | 19:36:26 | |
| All these questions arise from the .NET packages that depend on Linux DLLs | 19:40:23 | |
Corngood: quick question, how does nuget-to-nix determine what packages are SDK ones or not? | 22:01:10 | |
| It looks for packages that are installed in $NUGET_PACKAGES after restore. Packages from other build inputs are either not installed at all (they get referenced through $NUGET_FALLBACK_PACKAGES), or it skips them by:
To be clear this goes for all packages that come from other nix derivations, not just SDK ones (even though those are by far the most common right now). | 22:06:44 | |
| Hm, interesting | 22:07:16 | |
| I'm planning to make that thing you mentioned about referencing SDK packages | 22:07:25 | |
| and I'm gonna add them to the lockfile without a url (or a special URL) | 22:07:41 | |