choco

Chocolatey is quite good as well and in my opinion it does what it is supposed to. It only supports NuGet v2 which is becoming a problem, but being a open source project it's anyone's guess when improved NuGet support will be available. https://github.com/chocolatey/choco/issues/508 The big win with WinGet is mostly that it is a proper supported solution backed by Microsoft. But WinGet seems to require some more months before it is ready for primetime.

> chocolatey, who came up with that name The chocolatey repo (https://github.com/chocolatey/choco/wiki/History) explains the name as a pun based on the previous package manager NuGet: "Chocolatey started out as a joke because everyone loves Chocolatey nougat (nuget)."

“Neither”? Yes, Ninite is closed, e.g. https://ninite.com/help/notfeatures/more.html But alternatives aren’t: Chocolatey - Apache license - https://github.com/chocolatey/choco Homebrew (for Mac) - BSD license - https://github.com/Homebrew/brew Scoop (as previously mentioned) - Public Domain - https://github.com/lukesampson/scoop Comparing Scoop to Chocolatey: https://github.com/lukesampson/scoop/wiki/Chocolatey-Compari...

Apparently, Powershell requires a BOM to recognize UTF-8 scripts. https://github.com/chocolatey/choco/wiki/CreatePackages#char...

I wrote a little bit more about Chocolatey packaging, there is quite a bit of confusion about it because most folks only see the packages on the community feed (https://chocolatey.org/packags) and think that is the only way that Chocolatey works. https://github.com/chocolatey/choco/wiki/GettingStarted#what...

Only a download script for GUI apps? That's interesting and very likely misinformed. Since Chocolatey builds on top of NuGet.Core, it's got all of the same benefits to dependency resolution you get with NuGet. Plus it builds on top of that with quite a few things. You can call it a fancy download script if you want, but I think you are missing all of the things it does since it was rewritten last year - in addition to a download script, here are things it does currently - https://github.com/chocolatey/choco/wiki/GettingStarted#how-...

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. 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 suppo

Yes, and they've done some work on automatic uninstall so that there's less work required by packages to support uninstall: https://github.com/chocolatey/choco/wiki/CommandsUninstall