-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NuGet Runtime pack for community-supported architectures #42248
Comments
Adding @richlander @MichaelSimons for a policy discussion around these other architectures. |
This has been a problem for a long time. I think the gap here is a design.
I think this description captures the problem pretty well. |
This also affects .NET on IBM platforms (eg, |
AFAIK, the answer is currently no. The prefexes are reserved by Microsoft on nuget.org, and no one else can publish to the prefixes. Publishing under another prefix makes it non-trivial to consume, if it's possible at all. |
Right. A design would need to enable publishing the various packs under arbitrary names and to provide a registration mechanism, likely via a NuGet package (or something equivalent). |
Workaround: https://driver1998.github.io/posts/dotnet-cross-publish-loongarch/ |
Is your feature request related to a problem? Please describe.
.NET now has a few community-supported platforms:
linux-riscv64
,linux-loongarch64
, etc.And to properly support cross-publishing in .NET SDK, we need to get runtime packages from NuGet, otherwise publish will fail.
Hosting these packages on self-hosted repos are certainly an option, but is it possible now for maintainers to push those to NuGet.org under their own account? (Not as Microsoft because they won't be supported by Microsoft to begin with).
That way we can get a consistent publish experience.
The text was updated successfully, but these errors were encountered: