-
Notifications
You must be signed in to change notification settings - Fork 252
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
Finalize mechanism to distribute localized assemblies via dotnet pack #5186
Comments
This is already supported in NuGetizer (has mostly always been, rather?) |
Does nugetizer add all localized assemblies to the same nupkg? Or creates nupkg per culture? |
Adds the satellite resources to the main package |
In Humanizer, we need to create one package per culture and a metapackage that references all cultures. Would love to use pack targets for this but am currently blocked https://github.com/Humanizr/Humanizer/tree/dev/NuSpecs |
@onovotny pack targets already add satellite assemblies (if they are part of SatelliteDllsProjectOutputGroup) to the nupkg in the culture folder inside lib. Am i missing something that you require? |
@onovotny or is your expectation that pack should create an individual nupkg for each culture and a metapackage that references each of them? |
Yes....we require creating a language specific nupkg per satellite resource. Not including them in the main package. |
@onovotny can i ask why are you against putting all satellite resources in the main package? |
The expectation is that we should have that option. We are doing this because some users explicitly don't want all of the languages "polluting their output". I think it's silly, but it's what the users want. By using the satellite packages, people can choose the languages they want. Or they can use the main metapackage and get them all. |
No description provided.
The text was updated successfully, but these errors were encountered: