-
Notifications
You must be signed in to change notification settings - Fork 1
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
Install dedicated version of a package #57
Comments
It's sure possible but I did not have the usecase myself by now. Nodejs is an easy case to do it by hand by the way. |
First, let me say ChocolateStoreCore is very cool (I was doing basically the same thing, but editing the nupkg packages myself -which is not so much fun), especially that it iterates through any dependencies. I'm all for this as well (ability to specify a version). Here is a real-world example, I just encountered: I just tried downloading firefox, and ChocolateStoreCore.exe successfully gets version 127.0.2: I go to https://community.chocolatey.org/packages/Firefox -and the latest is actually 128.0.0, as per (released yesterday 07/09/2024): So, to avoid this sort of ambiguity of whatever the logic is (caching, 2nd to the latest version, etc.), could we simply have the ability to indicate the (optional) version in
Some reasons why:
For context, I'm using ChocolateStoreCore.exe to create the "corrected" packages (meaning external binaries are now local downloads), in the context of a Sonatype Nexus service:
Thanks, |
Should be fixed now. Use this syntax as suggested: |
I just tried it out, and it works great, many thanks! |
Would it be possible to specify a specific line in the download list to be of a specific version. Im trying to install a nodejs application offline and would need the LTS version of nodejs rather than the experimental. Similar to how you can install a dedicated version though the
choco
command withchoco install nodejs --version 20.15.0
The text was updated successfully, but these errors were encountered: