Skip to content

NuGet.Client does not support localization on Linux machines #12440

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

Open
NikolaMilosavljevic opened this issue Feb 17, 2023 · 1 comment
Open
Labels
Partner:DotNet Priority:2 Issues for the current backlog. Tenet:WorldReady Type:Engineering product/infrastructure work/not a customer bug/feature/DCR

Comments

@NikolaMilosavljevic
Copy link

Localization is not source-build compliant - it can not be executed on Linux machines. Linux distro owners has expressed desire to have localized resources of all binaries that ship with .NET SDK. Source-build runs on distro-specific machines and builds .NET SDK completely from sources - it does not consume any prebuilt binaries.

NuGet.Client repo uses NuGet.Build.Localization submodule for localization. That submodule provides tooling that is Windows and .NET FX specific.

@ghost
Copy link

ghost commented Feb 17, 2023

Issue is missing Type label, remember to add a Type label

@ghost ghost added the missing-required-type The required type label is missing. label Feb 17, 2023
@nkolev92 nkolev92 added Tenet:WorldReady Type:Engineering product/infrastructure work/not a customer bug/feature/DCR Partner:DotNet Priority:2 Issues for the current backlog. and removed missing-required-type The required type label is missing. labels Feb 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Partner:DotNet Priority:2 Issues for the current backlog. Tenet:WorldReady Type:Engineering product/infrastructure work/not a customer bug/feature/DCR
Projects
None yet
Development

No branches or pull requests

2 participants