Yes, I'd like to see this as well. Many other tools you might use in the terminal (it is a CLI package installer after all) are provided as standalone binaries. I'd like to package ffsend.

Existing package managers for Windows such as scoop or Chocolatey allow the installation of standalone binaries as well. Some inspiration might be taken from there.

I would love to be able to install tools like terraform, packer, kubectl, etc.. I could use scoop.sh, but I would love to have one tool to handle everything. winget should be able to install command line tools to a common directory in the user's directory but also make sure that directory is part of the path.

I'm looking for this support to package the CircleCI CLI tool.

👍

This is useful for the mob tool which is fundamental for remote mob programming. A release for windows is a single .tar.gz file containing a single .exe file.

Also useful for the ngrok tool for HTTP tunnelling.

To piggy back off of this, how would we go about installing applications like https://github.com/ggreer/the_silver_searcher where there will be no direct developer support for windows? There are unofficial windows builds but can those be considered?

I would like to be able to package a standalone app too, Yazz Pilot which is a single .exe file. Any estimate on when this will be coming?

Is there any update on this? I'd love to be able to package zoxide via WinGet. Being a command-line app, it is distributed as a single binary.

This would be a very useful feature for a lot of similar apps. Note that Scoop already supports this.

🎉 could you link us to the docs on how to develop for/use it? Thanks!

@bc3tech, we're holding off on accepting manifests for portable apps in the community repository until we've released the 1.3 client and most users have gotten the update. Instructions for authoring manifests will be updated at that point.

The specification provides some additional context on new arguments.

The 1.2 clients do not know about the new installer type which would cause a bad experience for users on the older version which is why we will wait until the client has rolled out more broadly. The community has been updating the PowerShell tooling in the Windows Package Manager Community Repository to help with manifest generation and testing.

The functionality is limited to local manifests today. winget install -m <path to directory with manifest>

fair enough, thanks for the context! I'm happy to await broader rollout as well :)

Is there any roadmap (or tracking issue, should I create one?) to add start menu entries for portable applications? This appears to be discussed as future considerations in the specification. I don't think it would add much complication, as I don't believe there are many edge cases (at least in the context of portable applications). It would be really nice for portable GUI applications to appear in the start/search menu.

@scottwillmoore

Feel free to create new issues. And, take a look at the general Roadmap.