| 3 Mar 2026 |
 Samuel | Yeah that wouldn't be great. | 00:29:03 |
 Corngood | Well I think the problem only occurs when you use `combinePackages`, right? And it happens to use symlinks | 00:36:41 |
 Whovian9369 | Anyone know how git-based fetchers work with repo tags? I have (someone else's) dotnet app building that is seemingly pulling an existing but old tag for VersionInfo.Version and I can't figure out how :P | 04:14:58 |
| Whovian9369 | I'm using the latest commit on master and not one on the tag, so I am a bit stumped on this. | 04:15:50 |
| Corngood | It's hard to imagine it's related to the fetcher itself? Is it set to keep .git? Is it something you can share? | 15:13:30 |
| 11 Mar 2026 |
 JamieMagee | I've been working on getting dotnet workloads working in our builds, and I have a PR that is ready for review
https://github.com/NixOS/nixpkgs/pull/498033 | 19:23:03 |
| 12 Mar 2026 |
 lostmsu | I just added a package for Android workload (the one you get by running dotnet workload install requires FHS) https://github.com/NixOS/nixpkgs/pull/499272 | 13:56:55 |
| lostmsu | fixing lint now | 14:02:59 |
| lostmsu | beats mine, I will close mine for now, see if Jamie's one lands | 14:10:05 |
| Corngood | I'm just working on the march release updates, which are going a bit slower than usual because they added support for building multiple feature band SDKs from source. I'll take a closer look at the workload stuff when I get some downtime | 15:02:43 |
| JamieMagee | Thanks for the review. I hadn't tested with the android workload, mainly aspire or wasm. Seems like there are still some gaps in my implementation. | 15:59:11 |
| lostmsu | did you test wasm one outside of the build script? | 16:00:28 |
| 13 Oct 2022 |
|  Winter (she/her) joined the room. | 17:56:01 |
| 12 Nov 2022 |
|  321, jiayou! joined the room. | 09:31:11 |
| 321, jiayou! left the room. | 09:31:52 |
| 16 Nov 2022 |
|  omlet joined the room. | 20:33:57 |
| 25 Nov 2022 |
|  raphi changed their profile picture. | 19:41:53 |
| 1 Dec 2022 |
|  hexa changed their display name from hexa to hexa (22.11 now). | 13:08:55 |
| hexa changed their display name from hexa (22.11 now) to hexa. | 14:38:43 |
| 12 Jan 2023 |
|  daniel joined the room. | 12:58:04 |
| daniel | Anyone who has some experience with packaging a .NET-project using flakes? All prior art I’ve found seems to use the legacy way. | 13:02:55 |
| Winter (she/her) | In reply to @daniel:nopemail.org
Anyone who has some experience with packaging a .NET-project using flakes? All prior art I’ve found seems to use the legacy way. flakes are the same way as the "legacy way," all flakes help with is exposing the package.
what trouble are you running into? | 14:23:13 |
| daniel | In reply to @winterqt:nixos.dev
flakes are the same way as the "legacy way," all flakes help with is exposing the package.
what trouble are you running into? How to "expose"/run fetch-deps | 14:24:38 |
| Winter (she/her) | just do nix build .#whateverPackage.fetch-deps | 14:25:11 |
| daniel | I did that over and over, realized now that I of course called it with the wrong package name. Thanks though! | 14:29:12 |
| Winter (she/her) | In reply to @daniel:nopemail.org
I did that over and over, realized now that I of course called it with the wrong package name. Thanks though! (was it not erroring?) | 14:31:10 |
| daniel | In reply to @winterqt:nixos.dev
(was it not erroring?) It was, but I thought that meant that somehow fetch-deps didn't pass through correctly. | 14:33:24 |
| 17 Jan 2023 |
| daniel | Fetch-deps doesn't seem to handle project references correctly, am I observing this right? The script wants to look for the project dependencies in the "nuget.org" source. | 11:07:33 |
| raphi | in my experience <ProjectReference> just works, as long both the referring project and the referenced project are part of src
example: https://github.com/raphaelr/nugettest
if they are separated search for projectReferences in the nixpkgs manual | 11:48:50 |
| 22 Jan 2023 |
| omlet left the room. | 20:26:21 |
