I have the following packages installed with Chocolatey.
choco list --localonly
One week later the GIMP package updated to 2.9 and the Git package is updated to 1.9.6 on the chocolatey.org website, but other packages are not updated.
Two weeks later I need to run a command in cmd to show the following result:
What is the good way to compose such command? (Or if there is a command option built into Chocolatey itself, what it would be?)
3 Answers
Note: You likely need to do the following commands in an administrative cmd/powershell prompt.
If you have version 0.9.8.33 or below installed:
If you have 0.9.9+ installed:
If you have choco 0.9.9.6+, you can use the outdated
command.
Following that, if you actually want to upgrade - in both versions you can follow with:
Note:-y
will only work with 0.9.8.33+.
Addition from @feventcoder
choco version all
will result you a warning of
DEPRECATION NOTICE - choco version
command is deprecated and will be removed in version 1.0.0. Please use choco upgrade <pgkname> --noop
instead.
So it mean you should learn that it might not support the version
command anymore.
Sure that you need to upgrade your chocolatey version to 0.9.9+ or latest.
By the command choco upgrade chocolatey
And then call cup all -y
to install all upgrade to your system.
The quickest way if you want to find only the local packages installed is to issue the following command to a DOS prompt:
Or even easier to remember and type:
This avoids unnecessary querying.
Not the answer you're looking for? Browse other questions tagged windowscommand-linechocolatey or ask your own question.
Is Chocolatey a higher version of NuGet or a different package manager? Where should I put my open source application? NuGet or Chocolatey?
1 Answer
NuGet is designed to allow you to easily add code libraries to your project. Things like JSON.NET, Entity Framework, etc.
Chocolatey is actually built on top of the NuGet package system, but it is designed to fill a different need. Chocolatey wraps up applications and other executables and makes it easy to install them on your computer. For example, tools like Git, Notepad++, etc. can be easily installed with a command like cinst git
.
https://chocolatey.org/packages has a list of all the applications that can be installed.
If you have an open source project which is a library that is to be used in other developers' projects, then you should submit it to NuGet.
If it is an application that users would normally install, then create a Chocolatey package that users can easily install and update from the command line.
Choco Package Manager
protected by cassiomolinFeb 28 at 17:03
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Not the answer you're looking for? Browse other questions tagged nugetchocolatey or ask your own question.
Well 'them' me and my team.It's likely building on top of NuGet was a mistake on my part, but it's all there was at the time and it was pretty easy to get started. We don't need the tools folder and we don't like the content folder.
Since Chocolatey does everything once the NuGet package is in place related to automation scripts, it doesn't really matter that v3 doesn't support the pre or post scripts. I started working with the NuGet team a couple of summers ago about making the format more flexible, this was just as v3 work was starting to get ramped up.
Package Manager Linux
At some point Chocolatey will likely not have any dependencies on NuGet itself, but will be compatible with NuGet packaging formats. To move more towards a machine package manager there are more things you need in the specification (like what versions of Windows does a package support as metadata, dependencies per OS, optional dependencies, virtuals, etc). Things that NuGet proper may never need.
How To Create Choco Package
My point being, Chocolatey has done a lot of growing up over the last year with a complete rewrite in C#, and will continue to grow up into a full fledged package manager over the next couple of years. There are some fundamental things we are still working out, but there are some amazing things in the pipeline coming for Chocolatey.
For whether we'd move from one format to the next isn't really a choice, it's a must. We'll need to do it in a backwards compatible way. https://github.com/chocolatey/choco/issues/508