Skip to content
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

Open
driver1998 opened this issue Jul 19, 2024 · 6 comments
Open

NuGet Runtime pack for community-supported architectures #42248

driver1998 opened this issue Jul 19, 2024 · 6 comments

Comments

@driver1998
Copy link

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.

@dotnet-issue-labeler dotnet-issue-labeler bot added Area-NetSDK untriaged Request triage from a team member labels Jul 19, 2024
@marcpopMSFT marcpopMSFT added needs team triage Requires a full team discussion and removed untriaged Request triage from a team member needs team triage Requires a full team discussion labels Aug 13, 2024
@marcpopMSFT marcpopMSFT added this to the Discussion milestone Aug 13, 2024
@marcpopMSFT
Copy link
Member

Adding @richlander @MichaelSimons for a policy discussion around these other architectures.

@richlander
Copy link
Member

This has been a problem for a long time. I think the gap here is a design.

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).

I think this description captures the problem pretty well.

@omajid @jkotas @baronfel

@omajid
Copy link
Member

omajid commented Aug 13, 2024

This also affects .NET on IBM platforms (eg, linux-ppc64le, linux-s390x)

cc @uweigand @Swapnali911

@omajid
Copy link
Member

omajid commented Aug 13, 2024

is it possible now for maintainers to push those to NuGet.org under their own account?

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.

@richlander
Copy link
Member

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).

@driver1998
Copy link
Author

driver1998 commented Dec 14, 2024

Workaround:
A guide (Chinese only) to manually extract runtime packs from native SDK to your build SDK for cross-publishing scenarios (like from win-x64 to linux-loongarch64):

https://driver1998.github.io/posts/dotnet-cross-publish-loongarch/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants