-
Notifications
You must be signed in to change notification settings - Fork 905
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
choco pack doesn't include chocolatey-specific metadata #607
Comments
The version of |
@bdukes Chocolatey doesn't use nuget.exe for packing. It uses a built-in Nuget.Core.dll. |
Ah NuGet... :/ |
This is fixed and will go out in a beta today. |
In NuGet.Core, manifest creation has a secondary path (an overload to `Create()` ) in 2.11 and they did not use a shared method to set the metadata that was alike. The DRY violation has been fixed so both `Create` methods now go through the same path to set similar metadata.
A beta just got pushed with these fixes. https://chocolatey.org/packages/chocolatey/0.9.10-beta-20160204
Would love some verification that this works. |
This addresses chocolatey/choco#607 - the manifest in 2.11 has a secondary path. I find it interesting that both are there doing nearly the same thing. Fixed this to both use a method to get Metadata so there is no longer a violation of DRY.
This addresses chocolatey/choco#607 - the manifest in 2.11 has a secondary path. I find it interesting that both are there doing nearly the same thing. Fixed this to both use a method to get Metadata so there is no longer a violation of DRY.
I believe this started yesterday when I installed the pre-release version of
chocolatey
andchoco.extension
package. I currently have version 0.9.10-beta1-116-ga1474ea installed.I updated the nuspec for hg, adding
docsUrl
,mailingListUrl
,bugTrackerUrl
, andreleaseNotes
(and already hadpackageSourceUrl
specified). However, when I submitted the package, the review indicated I still needed to add those elements. When I review the nupkg that is produced fromcpack
(orchoco pack
), I see that the nuspec doesn't include any of those new elements, exceptreleaseNotes
.The text was updated successfully, but these errors were encountered: