Skip to content
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.

Sign up for GitHub

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

Jump to bottom

When installing with *.nupkg, need to get package name from package, not file name #90

Closed
bdukes opened this issue Feb 9, 2015 · 6 comments
Closed

When installing with *.nupkg, need to get package name from package, not file name #90

bdukes opened this issue Feb 9, 2015 · 6 comments
Assignees
@ferventcoder
Labels
5 - Released Bug Priority_LOW Up For Grabs
Milestone
0.9.9.7

Comments

@bdukes
Copy link
Contributor

bdukes commented Feb 9, 2015

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#L233
@ferventcoder ferventcoder added this to the 0.9.9 milestone Feb 9, 2015
@ferventcoder ferventcoder changed the title When installing with *.nuspec or *.nupkg, need to get package name from package, not file name When installing with *.nupkg, need to get package name from package, not file name Feb 12, 2015
@ferventcoder ferventcoder modified the milestones: 0.9.10, 0.9.9 Feb 28, 2015
@zl4bv
Copy link

zl4bv commented May 5, 2015

Is there an alternative method of installing *.nupkg files from the local file system?

@ferventcoder
Copy link
Member

@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 -source "%cd%" or -source '$pwd' (or point to the folder of the package if it is not the current directory).

@ferventcoder
Copy link
Member

You can also point to the nuspec and it will work properly.

@ferventcoder
Copy link
Member

This is a bug on a new feature of choco, and it has a workaround, that's why the priority is low.

@zl4bv
Copy link

zl4bv commented May 5, 2015

The method detailed in the wiki that has been the way to do it since day one -source "%cd%" or -source '$pwd' (or point to the folder of the package if it is not the current directory).

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.

@ferventcoder ferventcoder mentioned this issue May 11, 2015
Closed
@ferventcoder ferventcoder modified the milestones: 0.9.9.7, 0.9.10 Jun 7, 2015
@ferventcoder ferventcoder self-assigned this Jun 7, 2015
ferventcoder added a commit that referenced this issue Jun 7, 2015
@ferventcoder
(GH-90) Fix install by nupkg file directly
4e39213 
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.
ferventcoder added a commit that referenced this issue Jun 7, 2015
@ferventcoder
(GH-90) Scenario for nupkg install
5a65295
ferventcoder added a commit that referenced this issue Jun 7, 2015
@ferventcoder
Merge branch 'stable'
062b97d 
* stable:
  (GH-90) Scenario for nupkg install
  (GH-90) Fix install by nupkg file directly
@ferventcoder
Copy link
Member

This has been implemented in 4e39213 and will be released with 0.9.9.7. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Bug Priority_LOW Up For Grabs
Projects
None yet
Milestone
0.9.9.7
Development

No branches or pull requests
4 participants
@bdukes @ferventcoder @gep13 @zl4bv