Choco package for v1.3.0

[apoorvdeshmukh]

Updating files required to prepare a choco package.
Tested as below
Updated sqlcmd.nuspec and tools\chocolateyinstall and ran choco pack sqlcmd.nuspec

git\go-sqlcmd\release\windows\choco>choco pack sqlcmd.nuspec
Chocolatey v2.1.0
Attempting to build package from 'sqlcmd.nuspec'.
Successfully created package 'git\go-sqlcmd\release\windows\choco\sqlcmd.1.3.0.nupkg'

Tested as per instructions here
No issues seen.

[shueybubbles]

1.3.0

can we have the pack script set the version from the tag instead of hard coding it here?

[apoorvdeshmukh]

The package script doesn't generate this file. Should we be generating this file as part of package script?

[shueybubbles]

no, the file can reference the version as a variable, and the pack command that generates the package from the nuspec can set the variable

[shueybubbles]

changing from the downloads site to github seems like a big deal. Do you know why we were using downloads before, and if there's any approval needed to stop using it?

And what is the value of $url here?

[apoorvdeshmukh]

I checked the download site for the previous version here and noticed that it is pointing to github. Thought of updating the files in our repo first to keep them in sync with choco. The choco command to push the package doesn't really rely on these files.

[shueybubbles]

File an issue to change how these files are generated. We should just have a template in the repo, and the official build should create the package by populating the template with the actual tag value and github locations and checksum.

[shueybubbles]

we shouldn't add nupkg files to the repo