| 10 Jan 2025 |
 6pak | but it feels like the outputs thing was literally designed for this | 17:09:16 |
 Corngood | I pasted the nuspec above to show the dependencies. If they were all separate, you'd have to do buildInputs = [ avalonia avalonia-remote-protocol ], etc. | 17:09:52 |
| Corngood | Unless we teach the builder to understand those dependencies and propagate them. | 17:10:13 |
| 6pak | can't you just use propagatedBuildInputs? | 17:10:28 |
| Corngood | yeah, but you need to get the dependencies from the nuspec:
<group targetFramework="net6.0">
<dependency id="Avalonia.Remote.Protocol" version="11.0.11" exclude="Build,Analyzers" />
| 17:10:56 |
| Corngood | and they depend on target frameworks, etc | 17:11:12 |
| 6pak | you could get it at avalonia's fetch-deps stage | 17:11:28 |
| 6pak | nuget restore includes figuring out projectreferences metadata | 17:11:44 |
| Corngood | it's the output of avalonia, so I think you'd have to do it in the dependent project's fetch phase? | 17:11:59 |
