dotnet pack doesn't let me provide my own nuspec

When I do “dotnet pack”, it synthesizes a .nuspec. This nuspec has several problems:

• Authors and Owners isn’t right
• requireLicenseAcceptance is wrong for my package
• URLs to license and product and icon are wrong
• It only has one dependency group on “.NETStandard”, but I wish to provide additional dependency groups so that UWP and .NET46 can consume my nuget package too

I wish to provide my own .nuspec file for it to use instead.

Expected behavior

If I do “dotnet pack” and my working directory already contains a .nuspec file, then it should use that.

Or: if I do “dotnet pack -h” then it should provide information on how to provide my own nuspec file.

Actual behavior

It doesn’t do either.

Environment data

dotnet --version output: 1.0.0-beta-002133 on OSX

[derekgreer]

“dotnet-pack is going to be replaced by nuget pack” - https://github.com/dotnet/cli/issues/2893

And here I thought dotnet pack was intended to replace nuget pack. This tooling thrash is bonkers!

Okay, so as of April 23, 2017, should we be using nuget pack or dotnet nuget pack? If we use dotnet pack, is supporting separate nuspec files planned? Ultimately, I’m wondering how you’d go about specifying you’d like the spec to generate dependencies with ranges (e.g. <dependency id=“System.Logging” version=“[1,2)” />).

[plioi]

You can use dotnet pack against a project, and that csproj can include <NuspecFile>relative path here</NuspecFile> within a <PropertyGroup>. In order to get the right version number information into the nuspec, though, I have to have a build script generate that nuspec. I think what’s really missing is for this scenario to support the old $replacementtoken$ syntax, propagating values from the new csproj packaging tags.