-
Notifications
You must be signed in to change notification settings - Fork 1
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
Plans to add upgrade support? #68
Comments
Hi, |
Roco was recommended to me from this issue I posted on Chocolatey. In summary, Choco takes some time to upgrade packages because it parses the entire DOM for each package. I know I could just write a script to only upgrade the packages Or if there was a switch that would spit out the outdated package names only delimited by a space.. That way you could run |
I see... in the meantime, try
😉 🚀 |
@asheroto try removing the It is passing as a quoted string to Chocolatey (that is PowerShell doing that), without the join, then PowerShell should pass the package names correctly. |
omg it's like magic! lightning fast upgrades! thanks! literally < 60 seconds compared to 3-6 minutes. now if only chocolatey would natively support concurrency (non- Windows installer -based applications, of course). |
1.5 years later, I still think adding "upgrade support" to rocolatey is not the way to go - simply upgrading everything that can be upgraded without revisiting the list of update candidates can go very wrong and that's not something I want people to do by accident. On the other hand, I'm guessing a
|
Hey, thanks for building this!
Do you plan to add support for upgrading packages?
roco upgrade all
etc?The text was updated successfully, but these errors were encountered: