| 10 Jan 2025 |
 Corngood | Some do. Some have dependent packages like skiasharp.native.linux, but there's also all the TFM variants of assemblies. | 16:04:17 |
 GGG | I don't think there's much we can do without actually reproducing nuget's logic for restoring packages to know what will actually be used | 16:09:35 |
| GGG | And even if we did, one package could use the net8.0 assembly and the other could use net7.0 | 16:10:14 |
| Corngood | Yeah, and both could be used in a dependent package. Nuget packages are not really designed to be runtime dependencies. It still might be worth doing though, even if it's just to reduce the size of the leaf packages. | 16:53:22 |
 6pak |
you're only linking to one of them, but pulling the whole package into the closure.
could we use multiple derivation outputs for this?
| 16:53:59 |
| 6pak | also whats the cost of adding more derivation/store objects in nixpkgs | 16:55:10 |
| 6pak | I mean eval time and storage wise | 16:55:14 |
| 6pak | it feels like splitting things up is discouraged | 16:55:48 |
| Corngood |
could we use multiple derivation outputs for this?
potentially, but you'd need to know at eval time how to split it up, so it would have to be done fetch-deps or something
| 16:56:37 |
| Corngood | I also want to end up with a good experience for source-built packages, and there's another layer of complexity there. Take 'avalonia' for example. That's one repository with one build process, but it results in a whole bunch of nuget packages. These all have dependencies between each other, and only some will be used by a dependent project. So for one nixpkgs package (avalonia) you currently have one output that contains all the nuget packages, and each one of those potentially contains multiple sets of assemblies for different target frameworks. | 16:59:11 |
| Corngood | * I also want to end up with a good experience for source-built packages, and there's another layer of complexity there. Take 'avalonia' for example. That's one repository with one build process, but it results in a whole bunch of nuget packages. These all have dependencies between each other, and only some will be used by a dependent project. So for one nixpkgs package (avalonia) you currently have one output that contains all the nuget packages, and each one of those potentially contains multiple sets of assemblies for different target frameworks (this might not be the case for avalonia if it's all built for a single TFM). | 16:59:48 |
| Corngood | Actually here's an example of part of the output of that package:
result/share/nuget/packages/avalonia.win32
result/share/nuget/packages/avalonia.win32/11.0.11
result/share/nuget/packages/avalonia.win32/11.0.11/_rels
result/share/nuget/packages/avalonia.win32/11.0.11/_rels/.rels
result/share/nuget/packages/avalonia.win32/11.0.11/lib
result/share/nuget/packages/avalonia.win32/11.0.11/lib/net6.0
result/share/nuget/packages/avalonia.win32/11.0.11/lib/net6.0/Avalonia.Win32.dll
result/share/nuget/packages/avalonia.win32/11.0.11/lib/net6.0/Avalonia.Win32.xml
result/share/nuget/packages/avalonia.win32/11.0.11/lib/netstandard2.0
result/share/nuget/packages/avalonia.win32/11.0.11/lib/netstandard2.0/Avalonia.Win32.dll
result/share/nuget/packages/avalonia.win32/11.0.11/lib/netstandard2.0/Avalonia.Win32.xml
result/share/nuget/packages/avalonia.win32/11.0.11/Icon.png
result/share/nuget/packages/avalonia.win32/11.0.11/package
result/share/nuget/packages/avalonia.win32/11.0.11/package/services
result/share/nuget/packages/avalonia.win32/11.0.11/package/services/metadata
result/share/nuget/packages/avalonia.win32/11.0.11/package/services/metadata/core-properties
result/share/nuget/packages/avalonia.win32/11.0.11/package/services/metadata/core-properties/3ce73e06f9b745b9ba18ebd32b8b7f22.psmdcp
result/share/nuget/packages/avalonia.win32/11.0.11/[Content_Types].xml
result/share/nuget/packages/avalonia.win32/11.0.11/avalonia.win32.nuspec
result/share/nuget/packages/avalonia.win32/11.0.11/.nupkg.metadata
result/share/nuget/packages/avalonia.x11
result/share/nuget/packages/avalonia.x11/11.0.11
result/share/nuget/packages/avalonia.x11/11.0.11/_rels
result/share/nuget/packages/avalonia.x11/11.0.11/_rels/.rels
result/share/nuget/packages/avalonia.x11/11.0.11/lib
result/share/nuget/packages/avalonia.x11/11.0.11/lib/net6.0
result/share/nuget/packages/avalonia.x11/11.0.11/lib/net6.0/Avalonia.X11.dll
result/share/nuget/packages/avalonia.x11/11.0.11/lib/net6.0/Avalonia.X11.xml
result/share/nuget/packages/avalonia.x11/11.0.11/lib/netstandard2.0
result/share/nuget/packages/avalonia.x11/11.0.11/lib/netstandard2.0/Avalonia.X11.dll
result/share/nuget/packages/avalonia.x11/11.0.11/lib/netstandard2.0/Avalonia.X11.xml
result/share/nuget/packages/avalonia.x11/11.0.11/Icon.png
result/share/nuget/packages/avalonia.x11/11.0.11/package
result/share/nuget/packages/avalonia.x11/11.0.11/package/services
result/share/nuget/packages/avalonia.x11/11.0.11/package/services/metadata
result/share/nuget/packages/avalonia.x11/11.0.11/package/services/metadata/core-properties
result/share/nuget/packages/avalonia.x11/11.0.11/package/services/metadata/core-properties/25dfe1363a50409a81b44789515624d8.psmdcp
result/share/nuget/packages/avalonia.x11/11.0.11/[Content_Types].xml
result/share/nuget/packages/avalonia.x11/11.0.11/avalonia.x11.nuspec
result/share/nuget/packages/avalonia.x11/11.0.11/.nupkg.metadata
| 17:00:33 |
