4 ms·

> automatically running `brew update` with every brew command run This is not accurate. We run a minimal version of `brew update` at most once per minute when

> automatically running `brew update` with every brew command run This is not accurate. We run a minimal version of `brew update` at most once per minute when you run `brew install` or `brew upgrade`: https://github.com/Homebrew/brew/blob/5504e2c1320d52f8a92a33c90c313a47668979c0/Library/Homebrew/brew.sh#L237 https://github.com/Homebrew/brew/blob/5504e2c1320d52f8a92a33... You can set this interval with `HOMEBREW_AUTO_UPDATE_SECS` and disable this functionality with `HOMEBREW_NO_AUTO_UPDATE`.

falcolas 10y ago
> at most once per minute Well, that's a relief. I run an average of 4-5 brew commands every minute, so at least there's that. /s > when you run `brew install` or `brew upgrade` So, only the two most used `brew` commands (for me, at least) will trigger a series of git fetches and merges over the network and an in-place update of the code. > You can [...] disable this functionality with `HOMEBREW_NO_AUTO_UPDATE` Why was it enabled automatically in the first place? Why wasn't I notified when homebrew updated that this was the new default behavior. Why must I always dive into homebrew on github to identify (1) why it's not behaving the way I would expect a package manager to and (2) how to get back sane package manager behavior?
- mikemcquaid 10y ago
  > will trigger a series of git fetches If there's been no updates there will be no `git fetch` run. We use a newish GitHub API to check for updates as its quicker. > Why was it enabled automatically in the first place? A significant numbers of our created issues are due to people having failures when they don't run `brew update`. This solves that. > Why must I always dive into homebrew on github to identify (1) why it's not behaving the way I would expect a package manager to and (2) how to get back sane package manager behavior? We're an open-source project run by volunteers for free in our spare time. We're underfunded and understaffed so our communication is lacking. The best current place to find out about such things is to follow our issue tracker. We aim to improve this in future.

falcolas 10y ago

> at most once per minute Well, that's a relief. I run an average of 4-5 brew commands every minute, so at least there's that. /s > when you run `brew install` or `brew upgrade` So, only the two most used `brew` commands (for me, at least) will trigger a series of git fetches and merges over the network and an in-place update of the code. > You can [...] disable this functionality with `HOMEBREW_NO_AUTO_UPDATE` Why was it enabled automatically in the first place? Why wasn't I notified when homebrew updated that this was the new default behavior. Why must I always dive into homebrew on github to identify (1) why it's not behaving the way I would expect a package manager to and (2) how to get back sane package manager behavior?

mikemcquaid 10y ago
> will trigger a series of git fetches If there's been no updates there will be no `git fetch` run. We use a newish GitHub API to check for updates as its quicker. > Why was it enabled automatically in the first place? A significant numbers of our created issues are due to people having failures when they don't run `brew update`. This solves that. > Why must I always dive into homebrew on github to identify (1) why it's not behaving the way I would expect a package manager to and (2) how to get back sane package manager behavior? We're an open-source project run by volunteers for free in our spare time. We're underfunded and understaffed so our communication is lacking. The best current place to find out about such things is to follow our issue tracker. We aim to improve this in future.