winget-create VS appget

This workflow uses Windows Package Manager Manifest Creator to update and submit a new version of a package manifest

Yes, any installer (MSIX, MSI, EXE) may be added (https://github.com/microsoft/winget-pkgs). There is even a new tool the Windows Package Manager Manifest Creator (https://github.com/microsoft/winget-create) to make it easier to build a manifest and submit it to the GitHub repository. Portable / Stanalone .exe files and .zip files aren't supported yet, but they are on the backlog.

You can also add your programs or packages by executing winget install wingetcreate to install the Windows Package Manager Manifest Creator. Once the tool has been installed, execute wingetcreate new provide the URL to the installer. Then the tool will download the installer, parse it to determine any of the manifest values available in the installer, and guide you through the process to generate a valid manifest. If you provide your GitHub credentials when prompted, it will even fork the repository, create a new branch, submit a pull request, and provide you the URL to track its progress.

It has been admitted.

This is what an 'extinguish' looks like after embracing the idea of a Windows package manager by interviewing the creator of AppGet [0][1] and then dumping him to skip the extend part to full on copy it [2] with no credit and bundling it in the OS.

This is a rare straight extinguish after an embrace, especially in open source.

[0] https://keivan.io/the-day-appget-died/

[1] https://appget.net/

[2] https://www.theverge.com/2020/5/28/21272964/microsoft-winget...

One thing to keep an eye on is Microsoft's winget. Based off 'AppGet' but unfortunately MS don't prominently allude to winget's origins, although they have offhand mentioned it.