Repository navigation
Support for installation of portable/standalone apps #182
Description
Activity
- changed the title
[-]Support for installation of Portable apps[/-][+]Support for installation of portable/standalone apps[/+]on May 19, 2020 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.
Reacted by 百地 希留耶, Dennis Gaida, Oleksii Filonenko, Suhail Malik, magicgoose, bb010g, xparadoxical, glenn wolfe and Ryouko KonpakuI 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.
Reacted by 百地 希留耶, Oleksii Filonenko, JoBrad, magicgoose, Rohit Mistry and Romain- added this to the milestone
on May 23, 2020 I'm looking for this support to package the CircleCI CLI tool.
👍
Reacted by 百地 希留耶 and Abhi SohalThis is useful for the mob tool which is fundamental for remote mob programming. A release for windows is a single
.tar.gzfile containing a single.exefile.Also useful for the ngrok tool for HTTP tunnelling.
Reacted by Jani Hyytiäinen and AskPlaysTo 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?
- modified the milestones: ,
on Aug 24, 2020 We're targeting milestone 18 for this.
Reacted by Ajeet D'Souza, Tim Visée, lucas schneider, Dawid Gosławski, Cameron Taggart, Aram Panasenco, bb010g and Jo14 remaining items
Hey all, I'm working on the specification for portable / standalone applications. I'm hoping to get through an engineering review to look for missed edge cases this week. I'll be posting the specification after that, and another PM/Security/etc... review.
Reacted by Scott Moore, codgician, Mark Penner, soredake, Sebastian Zanoni, Nikolas Grottendieck, Rob Cannon, Kevin Locke, 百地 希留耶, Aram Panasenco and 5 moreNote: This will not include compressed files like an .exe inside of a .zip. I want to get this specification completed before moving on to the more complex set of edge cases for compressed files containing portable / standalone executables or other "nested" installers.
Reacted by Gerardo GrignoliDiscussion at: #1887
- added a commit that references this issue
on Mar 16, 2022 - linked a pull request that will close this issuePortable Support as Stable Feature #2233
on Jun 11, 2022 🎉 could you link us to the docs on how to develop for/use it? Thanks!
Reacted by Kevin Locke and Mark PennerReacted by Cengiz IlerlerBrandon H (@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>Reacted by Brandon H, 百地 希留耶, Benjamin Kane, Easton Pillay and Ebertfair 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.
Reacted by Yuki Ito and Brandon HFeel free to create new issues. And, take a look at the general Roadmap.
Reacted by Scott Mooreblocks #30972
Description of the new feature/enhancement
There are programs like starship or aria2, which only provide portable archived files.
There maybe also some apps just releases an standalone .exe file.
Although we can request they to build an msi/msix package, it will be more convenient if we support to install them directly.
For the portable apps, the install may mean extract the archive to Program Files, then create a shim-like redirection for the program, put it into a specific directory, and add the directory to PATH.
Related:
Edited by Demitrius Nelon (@denelon)