Chocolatey VS winget-cli

While the ArchWSL and Fedora WSL at MS Store may seem great at first before installing, these distros have often showed compatibility issues and sometimes very weird bugs; even conflicts with scoop or chocolatey apps.

Chocolatey Windows software management solution, we use this for installing Python and Deno

Authenticating with Kyma is a (in my opinion) unnecessary challenge as it leverages the OIDC-login plugin for kubectl. You find a description of the setup here. This works fine when on a Mac but can give you some headaches on a Windows and on Linux machine especially when combined with restrictive setups in corporate environments. For Windows I can only recommend installing krew via chocolatey and then install the OIDC plugin via kubectl krew install oidc-login. At least for me that was the only way to get this working on Windows.

On a Windows machine, you can use Chocolatey by running the command.

I've used WSL2 and GHC/Nix--worked without any issues. However, there is Chocolatey: https://chocolatey.org/

For OSX there is homebrew or pyenv (pyenv is another solution on Linux). As pyenv compiles from source it will require setting up XCode (the Apple IDE) tools to support this which can be pretty bulky. Windows users have chocolatey but the issue there is it works off the binaries. That means it won't have the latest security release available since those are source only. Conda is also another solution which can be picked up by Visual Studio Code as available versions of Python making development easier. In the end it might be best to consider using WSL on Windows for installing a Linux version and using that instead.

Type the following commands on the Windows terminal to install helm. You can use either Scoop a command-line installer for Windows or Chocolatey which is a Package Manager for Windows to install helm.

Winget seems to finally do something similar for Windows: https://github.com/microsoft/winget-cli

Although the "repo" is a list of manifest files that include download sources on GitHub and Sourceforge (and maybe others). So even if there is an approval process it seems to be quite vulnerable to including malware.

Microsoft seems to use a similar bot themselves, not sure how it is called or whether it is OSS: https://github.com/microsoft/winget-cli/issues/4765#issuecom...

It's not only tedious but also gets complicated because sometimes --id doesn't work as expected, as mentioned [here] the famous pnpm.pnpm (https://github.com/microsoft/winget-cli/issues/4751). So, you often need to use --name instead of --id.

For instance, on a Windows system, you would use winget and run the following command: winget install s3scanner. Your output would look like this:

The Winget module is a wreck. The way it is designed, unfortunately, neither fits the object oriented approach of PowerShell nor follows the PowerShell guidelines for cmdlets.

For instance https://github.com/microsoft/winget-cli/issues/3820 or https://github.com/microsoft/winget-cli/issues/3231.

Step 1: Download under this link Please use either link ok: https://learn.microsoft.com/en-us/windows/package-manager/winget/ https://github.com/microsoft/winget-cli/releases The file will look like Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle

https://github.com/microsoft/winget-cli

For both Windows 10 and 11, every application and system package gets installed via winget import --import-file {{JSON-file}}, when possible. It's shipped as a component of the App Installer package, which is supplied with Windows 11 but optional for Windows 10.

REALIX HWiNFO: https://www.hwinfo.com/

GitHub

Source: https://github.com/microsoft/winget-cli/issues/3832

You're correct here, and that's exactly the reason Winget is a package manager, as dependency management is part of teh stable release since version 1.6.3133: