-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for filtering packages on installer method #823
Comments
This feature is required prior to accepting "interactive only" installers into the community repository. Many users are looking for headless/unattended import capabilities. |
`Logitech.LGH` has been failing for several months now - might as well remove it if it can't run in unattended mode: https://github.com/microsoft/winget-pkgs/pulls?q=is%3Apr+author%3Awingetbot+Logitech+is%3Aclosed+
Currently, user interaction is needed for install: ![image](https://user-images.githubusercontent.com/11600822/120943923-b89fd080-c729-11eb-8d4c-5e50f1aa15b6.png) Blocked by microsoft/winget-cli#823.
Note: May not be suitable for inclusion in winget-pkgs due to requiring user interaction for driver certificate trust confirmation: microsoft#29306 (review) Waiting on microsoft/winget-cli#823 (comment) Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Note: May not be suitable for inclusion in winget-pkgs due to requiring user interaction for driver certificate trust confirmation: microsoft#29306 (review) Waiting on microsoft/winget-cli#823 (comment) Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
Would love to see this get looked at again. Requiring silent installation is a blocker for many programs. Notable ones include HP Support Assistant and Samsung Magician. Add a boolean indicator in the manifest like InteractiveInstallOnly. |
Currently we have |
Several packages do not support or provide a silent install experience.
Assuming package manifests identify support for interactive installers, the client should be able to filter these packages so they aren't inadvertently executed for certain scenarios. The client should be able to support a preference for silent install experiences if specified. Additionally the client should be able to filter search results so that packages requiring interactive install can be omitted.
This could be implemented in settings, as well as via command-line arguments.
The text was updated successfully, but these errors were encountered: