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
Add HOMEBREW_UPGRADE_GREEDY="auto-updates" and "latest" #16735
Comments
Given we already have Also, I think we should deprecate |
I'm happy to update my pull request with any preferred approach. Do you have a preference between adding |
Let's modify |
--greedy*
options in HOMEBREW_CASK_OPTS
Updated #16736 to modify |
Closing this out as we don't need an issue and PR from same author at same time and to keep conversation in one place. Thanks for the PR @jck112! |
Verification
brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.Provide a detailed description of the proposed feature
Many users, myself included, prefer to always run
brew upgrade --greedy-auto-updates
in order to upgrade all of our formulas and casks. Adding support for--greedy
,--greedy-latest
, and--greedy-auto-updates
to theHOMEBREW_CASK_OPTS
environment variable enables users to runbrew upgrade
more easily with their preferred cask upgrade options.What is the motivation for the feature?
Pull request #15160 added support for the
HOMEBREW_UPGRADE_GREEDY
environment variable, but deferred adding support for the--greedy-latest
and--greedy-auto-updates
options. I believe adding support for these additional options viaHOMEBREW_CASK_OPTS
provides a potentially simpler and more streamlined solution.How will the feature be relevant to at least 90% of Homebrew users?
As discussed in #15097, there are many users using the
--greedy-auto-updates
option in particular.What alternatives to the feature have been considered?
Alternatively new environment variables could be added, e.g.
HOMEBREW_UPGRADE_GREEDY_LATEST
andHOMEBREW_UPGRADE_GREEDY_AUTO_UPDATES
.The text was updated successfully, but these errors were encountered: