microsoft / microsoft/winget-cli
--silent should redirect stdout to the log file
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 installers (Docker Desktop and the modern SQL Server installer are the ones I know) send lots of log output to stdout when they are ran silently. This makes the winget progress information go away:
Users have found this confusing and have requested that if winget runs a package silently, it is truly silent (i.e. they see nothing except Starting package install...). My solution to that problem is that when the --silent argument is used, winget should redirect stdout for the installer to a log file (much like MSIs, this should be selectable via a argument).
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 by tracing how the --silent argument launches installers and handles their stdout. Done means silent installs no longer obscure winget progress, while installer output is redirected to a log file whose destination can be selected by an argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100