microsoft / microsoft/winget-cli
Support install location via import
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Is the following command possible?
winget import -i <import-file> —location <path>
If not, how can I use the import command to control where it should be installed?
Originally posted by @PhilippBaumi in https://github.com/microsoft/winget-cli/discussions/1521#discussioncomment-1467325
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 tracing the winget import -i <import-file> --location <path> command and how imported package options are passed to installers. Clarify whether import should apply one location to all packages and how packages that do not support custom locations should behave; done means the expected behavior is implemented and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100