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 HOMEBREW_GREEDY or variants #15097
Comments
Back when this was introduced I was already arguing that |
I think that it probably makes sense to just start with |
Yeah, I don't think we need all variants. The vast majority of casks are also versioned now, so |
Or we can just use
|
Agreed. I'd be 👍🏻 to have just this implemented for now. |
Personally I run The biggest difference for me is that I wouldn't use the environment variable myself, as I have shell commands to handle these, but just wanted to mention the extra network usage for |
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
Would be nice if Homebrew supported the following env variables:
HOMEBREW_GREEDY
HOMEBREW_GREEDY_LATEST
HOMEBREW_GREEDY_AUTO_UPDATES
When set, the commands that accept respected flags (
--greedy
,--greedy-latest
, and--greedy-auto-updates
) should behave as this flag was set even if it wasn't. Would be nice ifbrew autoupdate start
will also support it.What is the motivation for the feature?
I'm used to running
brew upgrade --greedy
all the time, and it seems like there is no environment variable to set this flag by default.How will the feature be relevant to at least 90% of Homebrew users?
This feature is relevant for everyone who is always using
--greedy
and embeds it in the custom shell functions (e.g., Stack Overflow, GitHub).What alternatives to the feature have been considered?
The alternative is already implemented –
--greedy
flag and friends, but it is not really convenient to type it every upgrade.Also, any other variable names with the same functionality would also be appreciated.
The text was updated successfully, but these errors were encountered: