Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
The projects containing the static extensions are generally not part of any NuGet. #2094
I believe the projects with the name pattern Microsoft.ML.*.StaticPipe were created setting apart the static extensions so they can be on a separate nuget package.
Most of them are currently part of no package. There exists a main package for the main project containing the static pipe: Microsoft.ML.StaticPipe.
Note: this issue can be closed when all the projects containing static extensions are part of NuGet packages, depending on the resolution of the question above.
Thanks Senja for the issue.
As part of #1914, we created separate 5 assemblies for static extensions. These assemblies are named corresponding to nuget packages (with the Microsoft.ML prefix)
A. There should be two more assemblies that we should add to the list:
B. Nuget story for the Static API ?
I think we should add these static pipe nugets as part of v0.10, but for v0.9 you are correct we deliberately only shipped the "main" one as part of a nuget.
The ideal situation is separate nugets, I think. It would be nice if the "core" nuget package references only a few small nugets. Anything referencing a larger nuget, should be in its own nuget and not bundled with that. That in mind @abgoswam's project should provisionally be considered to reflect the desired nuget story.
These should each have separate nugets, if the things they depend on have separate nugets, which they all do. I considered these unessential to ship as part of v0.9 though considering the limited timeframe.