microsoft / microsoft/winget-cli
Post-Install Dependencies
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
Some packages like Google.Chrome.EXE have additional conponents like Google.GoogleUpdate required to make them run properly or to enable the full functionality of the package
However, in the example above, installing Google.GoogleUpdate first will result in a successful return code even though Google.GoogleUpdate won’t be installed. Installing it after installing Google.Chrome.EXE however does result in a successful install.
This means that it cannot be set as a dependency of Google.Chrome.EXE as the dependencies are installed first.
It would be beneficial to specify additional packages to be installed after the initial install is completed
- Related to #3928
Proposed technical implementation details
No response
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 with this issue and the related #3928 to understand the proposed post-install dependency behavior. Identify the package installation flow and how dependencies are currently ordered; done means a package can declare additional packages that install after the initial package succeeds, including the Google.Chrome.EXE and Google.GoogleUpdate scenario.
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
- Mostly clear
- Newbie friendliness
- 35/100