Package management tool "winget" for Windows, which has also been distributed to the general public, is v1.1

　Winget, a package management tool for Windows 10/11, reached Ver.1.0 on May 27th of this year. As a result, distribution as a stable version was started. On September 27th, preview version Ver.1.1.1270 and stable version Ver.1.1.12653 were released. Here, Winget is described based on this latest preview version.

Winget reached stable version v1.0 in May of this year and started to be distributed to the general public. v1.1 appeared at the end of September

What exactly is Winget?

　Let's introduce Winget again. Officially called "Windows Package Manager Client", it is one of Microsoft's open source software. Due to the length of the name, we refer to it as "Winget" in this article.

By using winget, it is possible to install and search for application packages registered in sources (general package manager repositories). Sources currently include Winget-only and some applications from the Microsoft Store. As for Winget, we have dealt with the preview version so far, so please refer to the following article for an overview.

●Package manager "winget" under development on Windows is v0.3 ●What happened to the package manager "winget" that can install Windows applications from the command line? Try the preview version of winget, the package manager for Windows 10

Windows Package Manager, which includes a manager for program distribution

　Next, "Windows Package Manager" is Wingetcreate, the software that creates Manifest files for registering with this Winget and the repository, and third-party It consists of three elements called Community Repository, which is a repository for Win32 applications (more precisely, a place to register Manifest files for registration in the repository).

・Windows Package Manager https://docs.microsoft.com/ja-jp/windows/package-manager/・Windows Package Manager Client (Winget)https://github.com/microsoft/winget-cli・Windows Package Manager Manifest Creator (WingetCreate) https://github.com/microsoft/winget-create・Windows Package Manager Community Repository https://github.com/microsoft/winget-pkgs/

For the time being, if you just want to install an app, you can use only Winget, but if you want to register your own programs, you need to look at the remaining two. Also, since the GitHub Community Repository has a manifest file for the registered application, it might be a good idea to look here if you can't find it with just the Search command.

　With regard to Winget, it is included in the "App Installer" of the Microsoft store, so if you have installed software that requires an app installer, such as Windows Terminal, you should already have Winget installed. . If you prefer to install it manually, the easiest way is to get the app installer from the Microsoft store. Alternatively, you can get the msix package from GitHub mentioned above and install it manually.

Ver.1.1 improvements, etc.

Winget specifies actions with subcommands and detailed actions with options.

　The options that can be specified with each subcommand are as follows.

　In addition, the source subcommand requires six subcommands, "add", "list", "update", "remove", "reset", and "export", and the options are as follows.

　Of these, the settings subcommand outputs a json file and opens the editor associated with ".json" (if nothing is set, the editor is selected first). Here you can specify options that specify how Winget behaves, including the following settings:

Specifically, create a json file like the list below. For information on how to search, please refer to the previous article mentioned above.

{ "source": { "autoUpdateIntervalInMinutes": 240 }, "visual": { "progressBar": "rainbow" }, "installBehavior": {"preferences": {"scope": "machine","locale ": ["en-US","en-US"] } }, "telemetry": { "disable": true }, "network": {"downloader": "do","doProgressTimeoutInSeconds": 60 }, "experimentalFeatures": {"dependencies":true,"directMSI":true }}

　Options added after v0.4 are displayed in red. The added options "--accept-package-agreements" and "--accept-source-agreements" accept the package and source licenses, respectively, without asking the user. .

　In the previous version, when installing with Winget, a message was displayed saying that Microsoft did not accept any license regardless of the license, but it seems that the license can be confirmed if specified on the package side. These are intended for automatic installation using scripts, etc. However, at the moment there are only two sources, one from Microsoft and the Microsoft store, and sites that require permission to use the source are not registered by default. However, if you want to use it in a script, etc., it would be better to specify these in advance.

"--header" is used together with "--source" to specify the option string attached to the HTTP header during REST access. Sources currently registered with Winget (winget and msstore) do not need to be specified.

　Experimental features are set with the settings subcommand, but the status can be checked with the features subcommand. There are two experimental functions: "directMSI" and "dependencies". "directMSI" instructs to install the msi format package directly using MSIAPI instead of Windows Installer. "dependencies" displays the dependency information of the package.