Improve brew update
with HOMEBREW_INSTALL_FROM_API
#13795
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modifies some
brew update
related logic to work better withHOMEBREW_INSTALL_FROM_API
. Currently, if you haveHOMEBREW_INSTALL_FROM_API
set,brew update
will never update the core and cask taps. We want this to remain, but also want a way for developers to continue maintaining homebrew/core and homebrew/cask. So, this PR modifiesbrew update
so that it does update the core and cask taps when someone withHOMEBREW_DEVELOPER
set runsbrew update
. As before.brew update --auto-update
will not update the core and cask taps.Additionally, I updated the call in
brew update
that updates the cached formula JSON file so that it uses--time-cond
like we do inHomebrew::API::Formula.all_formulae
to avoid unnecessary downloading when the file hasn't changed.Finally, I made a small change to
Homebrew::API::Formula.all_formulae
to remove a duplicated file path.