microsoft / microsoft/winget-pkgs
[New Feature]: Remove Legacy Installer Version for Portable Package
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
I have an application that ships with both an installer and a portable version. For WinGet distribution, I would prefer to use the portable package as it's a CLI-based tool.
However, if a user previously installed the app via the traditional installer, that version would take priority in the system (e.g., in the PATH), which can lead to confusion or unexpected behavior when the portable version is installed via WinGet.
Proposed technical implementation details (optional)
Add a manifest option that allows a WinGet package to specify that any existing installation of the same application installed with a different installer technology should be uninstalled (or optionally prompted for removal) before or during the installation of the new package.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the WinGet manifest schema and the issue's proposed behavior for portable packages and alternate installer technologies. Determine where such an option would be defined and how existing installation and removal flows are represented. Done means the behavior, prompting rules, and compatibility impact are specified well enough for implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100