| 10 Jan 2025 |
 Corngood | so you have four assemblies there, and a dependent project might only need one of them | 17:01:46 |
 6pak | could you have avalonia derivation output all those nuget packages in different outputs and then have dummy derivations like Avalonia.X11 that just link to one of the avalonia outputs? | 17:02:14 |
| 6pak | * could you have avalonia derivation output all those nuget packages in different outputs and then have dummy derivations like Avalonia.X11 that just links to one of the avalonia outputs? | 17:02:29 |
| 6pak | (I'm not really sure how nix derivation outputs thing works tbf) | 17:02:47 |
| Corngood | Yeah, I started building something like that, but instead of separate outputs I made separate derivations and pulled in parts of the monolithic one.
You do need to define the list of packages at eval time, which is annoying. | 17:03:48 |
| 6pak |
I made separate derivations and pulled in parts of the monolithic one
pull as in link or copy?
| 17:04:23 |
| Corngood | copy | 17:04:31 |
| Corngood | Where I got stuck is that I wanted the packages to depend on each other properly. Currently you can reference avalonia and get everything, but I didn't want dependent projects to have to list a bunch of transient dependencies in buildInputs | 17:04:53 |
| 6pak | because link would mean you still have everything in closure, copy means you have the same thing twice in store/cache | 17:04:58 |
| Corngood | right, I thought it would be better to favour build closure size for dependent projects | 17:05:49 |
