You want different things than Homebrew was designed to do, which is perfectly fine. But we make those constraints abundantly clear in our documentation, and they produce a vastly better user experience for 99% of our users.
(Beggars can't be choosers, etc. — I recognize the utility that Homebrew has provided to millions of people, that doesn't mean I can't mention its problems.)
When a particular package (or version) is widely adopted and difficult to migrate away from (like versions of LLVM, Postgres, or Python), we provide `@`-discriminated versions to allow people to migrate at their own pace. If there's a particular formula you want versioned that we don't currently, please open an issue so that we can discuss it!
I haven't met a single software developer who wants this. That's not to say your statement is incorrect -- I have no evidence stating otherwise -- but the idea boggles my mind.
Pleased to meet you Hope you guess my name But what's puzzling you Is the nature of my game
Where versioning matters, we have better tools than OS package managers now (ex Docker).
You should get out more. No offense.
Incremental pain, delivered early, is both corrective and less expensive over the long run. If you need to remain version-locked for a specific reason, that reason is likely to be locally scoped rather than global, in which case TFA describes an attempt to address your problem.
This is an unnecessary comment.
>Incremental pain, delivered early, is both corrective and less expensive over the long run. If you need to remain version-locked for a specific reason, that reason is likely to be locally scoped rather than global, in which case TFA describes an attempt to address your problem.
This rests on the assumption of a relatively homogenized software development industry without any consideration for, at least, critical systems building. There's a broad range of disciplines in this industry which do not -- and cannot -- adhere to the practices you mention.
I can't tell you the total number of wasted hours my previous organisation spent upon maintaining MacOS infrastructure after random breakage due to homebrew, but it was a regular occurrence and likely a few hundreds of hours per year for the small setup we looked after, mainly for CI.
On Linux I use a rolling release distro for the same effect.
That said, the insistence on everything updating all the time is very frustrating. Being stuck waiting 30 seconds when trying to install something because brew is updating despite no one asking it to, random things breaking after an update, and needing to find escape hatches so an older version of some package can be installed are all pretty painful.
Perhaps I too am in the minority here.
I really appreciate the work all the Homebrew developers do. But I've lost a lot of time chasing down problems caused just because I installed some stupid utility.
WFM. YMMV.
Thanks so much!
https://stackoverflow.com/questions/3987683/homebrew-install...
Maybe an appropriate amount of work if your context is sensitive to rolling updates.