-
Notifications
You must be signed in to change notification settings - Fork 902
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
When installing with *.nupkg, need to get package name from package, not file name #90
Comments
Is there an alternative method of installing *.nupkg files from the local file system? |
@zl4bv Yes, and that is why the priority is low. The method detailed in the wiki that has been the way to do it since day one |
You can also point to the nuspec and it will work properly. |
This is a bug on a new feature of choco, and it has a workaround, that's why the priority is low. |
Thanks - that's the way I've been installing packages. Wasn't sure if (ignoring the bug) Chocolatey behaves any differently by installing it this way. |
When issuing a command like `choco install hg.3.3.nupkg`, choco tries to find a package named "hg.3.3" (based on the passed in file name), rather the reading the manifest of the nupkg and finding the actual package name to install. Fix the behavior to allow calling install on the nupkg file directly.
This has been implemented in 4e39213 and will be released with 0.9.9.7. Thanks! |
When issuing a command like
choco install hg.3.3.nupkg
, choco tries to find a package named "hg.3.3" (based on the passed in file name), rather the reading the manifest of the nupkg and finding the actual package name to install. See https://github.com/chocolatey/choco/blob/master/src/chocolatey/infrastructure.app/services/NugetService.cs#L233The text was updated successfully, but these errors were encountered: