| 10 Jan 2025 |
 Corngood | yeah, maybe fetch-deps could determine something about the output packages. but still you have dependencies that are dependent on TFM. so a dependent project on net6.0 and netstandard2.0 might have different dependencies. you could be conservative and link all of them I guess | 17:12:58 |
 6pak | this would be bad though | 17:13:02 |
| Corngood | I didn't completely give up on it. this is just where it started to get hairy and I was trying to use the nuget sdk to figure out dependencies etc | 17:13:43 |
| 6pak | tbh listing it out manually might not be that bad | 17:14:11 |
| Corngood | yeah, maybe not. avalonia is probably about as complex as it gets | 17:14:31 |
| 6pak | yeah | 17:14:37 |
| Corngood | I want to get back to it at some point and make an up to date source build of avalonia that's actually used by things in nixpkgs | 17:14:52 |
| 6pak | and you can just have a meta package for avalonia in nixpkgs that includes all you need | 17:14:53 |
