You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I dislike seeing the installer when installing a Winget package, so my suggestion is to add an option in the settings to enable global silent install/uninstall/update option. An alternative would be to add a global install parameter.
By the way, --silent alone is enough for a silent install and --accept-package-agreements--accept-source-agreements are useless since Winget agrees with everything by default, right?
Related: #140 (for individual packages I believe) #44 (I didn't quite understand the discussion there about unattended/silent install. I know installation through WingetUI is unattended, why can't it be silent also?)
EDIT:
I think I figured out what you mean in #44. WingetUI uses --silent, but this command sometimes doesn't work properly, isn't it?
I've tested updating Pinta directly through Winget and through WingetUI. Both display a pop-up. However, this script apparently uses a workaround to have completely silent updates (I also found this comment interesting).
Would launching a hidden powershell/cmd window be enough to accomplish this or do you think it is a problem for Microsoft to fix?
On a second thought, I don't think a global install parameter would be useful to achieve a silent install. So, unless there's a reason, you may ignore it.
The text was updated successfully, but these errors were encountered:
--accept-package-agreements--accept-source-agreements are useless since Winget agrees with everything by default, right?
Nope, it does not, especially when there is msstore origin available (still asks if the argument --source winget is passed)
The issue with silent installs is that not every installer handles the same way the arguments. some require --silent, some require /verysilent and some other require other things (and passing them all would cause errors). That's why silent installs is not a thing that can be fixed from here but rather should fix the winget-cli project.
However, i've seen now the winget (not installer) --silent argument, i'm gonna test it and see if it works or not, but the main issue is with winget. (because scoop apps do not annoy when installed)
I dislike seeing the installer when installing a Winget package, so my suggestion is to add an option in the settings to enable global silent install/uninstall/update option. An alternative would be to add a global install parameter.
By the way,
--silent
alone is enough for a silent install and--accept-package-agreements
--accept-source-agreements
are useless since Winget agrees with everything by default, right?Related:
#140 (for individual packages I believe)
#44 (I didn't quite understand the discussion there about unattended/silent install. I know installation through WingetUI is unattended, why can't it be silent also?)
EDIT:
I think I figured out what you mean in #44. WingetUI uses
--silent
, but this command sometimes doesn't work properly, isn't it?I've tested updating Pinta directly through Winget and through WingetUI. Both display a pop-up. However, this script apparently uses a workaround to have completely silent updates (I also found this comment interesting).
Would launching a hidden powershell/cmd window be enough to accomplish this or do you think it is a problem for Microsoft to fix?
On a second thought, I don't think a global install parameter would be useful to achieve a silent install. So, unless there's a reason, you may ignore it.
The text was updated successfully, but these errors were encountered: