-
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 install relativepath/to/some.nuspec fails #906
Comments
I'm happy to take a look at this if nobody objects |
paulhunttech
pushed a commit
to paulhunttech/choco
that referenced
this issue
Jan 4, 2017
…ile. Previously when the install target was a nuspec file and the output folder was not set to the folder that contained the nuspec file then the installation failed because the nupkg file could not be found. Update sets the sources parameter to the output folder during the packaging of the nuspec file.
ferventcoder
pushed a commit
that referenced
this issue
Mar 22, 2017
Previously, when the install target was a nuspec file and the output folder was not set to the folder that contained the nuspec file then the installation failed because the nupkg file could not be found. Update sets the sources parameter to the output folder during the packaging of the nuspec file.
ferventcoder
added a commit
that referenced
this issue
Mar 22, 2017
* pr1127: (GH-906) Fix source path when installing "*.nuspec"
Fixed for 0.10.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For installs directly against a .nuspec, it appears that the .nupkg is runtime compiled into the working folder, but then when the call to 'install' is passed internally in choco, the source folder is given as the same folder as the .nuspec.
So if do this:
c:\somefolder> cinst -y subfolder\my.nuspec
The .nupkg ends up in "somefolder" but choco errors out that it can't find the package in c:\somefolder\subfolder.
choco version 0.10.0.
The text was updated successfully, but these errors were encountered: