undefined

points

[-]

This behaviour came about because, before we did that we ended up upgrading just what you wanted and breaking other packages by mistake.

It’s taken a long time but we’re finally at the point where we do (pretty much) only upgrade the minimal software we need to actually avoid breakage rather than the previous “better safe than sorry” conservative approach. We also now tell you by default everything we’ll upgrade before we do it (unless you say “upgrade foo” and all we are gonna do is upgrade foo).

So: we’ve maybe solved this issue and maybe not. The perfect outcomes for everyone here is pretty much impossible given the original design of Homebrew. MacPorts or Nix or Mise are likely a better fit in that case.

by lkbm17 hours ago|

prev|

[-]

Are you referring how it does a `brew upgrade` when doing a `brew install`? It should tell you how to disable that whenever it happens:

> Adjust how often this is run with `$HOMEBREW_AUTO_UPDATE_SECS` or disable with

> `$HOMEBREW_NO_AUTO_UPDATE=1`. Hide these hints with `$HOMEBREW_NO_ENV_HINTS=1` (see `man brew`).

by shikck20012 hours ago|

parent|

[-]

Why is this not the default? I removed homebrew years ago, because it was just full of nasty surprises like this. Does homebrew still share dependencies? Previously you could not have package A with a transitive dependency of lib-X = v1.2 and B that requires lib-X = v.0.7.