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
Add an option to pass multiple packages to winget at one time, like "winget install x y z" since it has it now, plus more ideas on ensuring we don't close in the middle of applying changes.
#169
Open
DrewNaylor opened this issue
Jun 8, 2023
· 0 comments
Need to figure out the order of "install", "uninstall", and "upgrade", though. Should I do uninstall first, then upgrade, then install? Hopefully specifying versions is possible too, otherwise that would be an issue.
Partially related due to how commands could get long and I may need to split things up a bit intelligently, I need to ensure we don't pass anything with "guinget" (or the package name that a hypothetical fork names itself; must be in the resources so that it's easy to change for a programmer) to winget until it's the last thing so that we don't close until we're ready to close if a user is updating us or whatever, as the Store restarts and stores the packages but we don't yet (ideally we need to store the list of package changes that need to be done if we get closed while applying changes; I made an issue somewhere about this but I forgot where).
The text was updated successfully, but these errors were encountered:
Need to figure out the order of "install", "uninstall", and "upgrade", though. Should I do uninstall first, then upgrade, then install? Hopefully specifying versions is possible too, otherwise that would be an issue.
Partially related due to how commands could get long and I may need to split things up a bit intelligently, I need to ensure we don't pass anything with "guinget" (or the package name that a hypothetical fork names itself; must be in the resources so that it's easy to change for a programmer) to winget until it's the last thing so that we don't close until we're ready to close if a user is updating us or whatever, as the Store restarts and stores the packages but we don't yet (ideally we need to store the list of package changes that need to be done if we get closed while applying changes; I made an issue somewhere about this but I forgot where).
The text was updated successfully, but these errors were encountered: