opensource.how VS homebrew-graph

> Homebrew is old and it needs to be replaced. It has served its time.

You are more than welcome to build your own alternative. Homebrew is open source and volunteer run. I'm sure there is a very valid reason requests like this get shot down.

No wonder open source maintainers hate dealing with people like you.

http://antirez.com/news/129

https://news.ycombinator.com/item?id=12000746

https://github.com/kossnocorp/etiquette

wat.

Of course the recursive update policy is going to be weirdly painful for some users! Homebrew doesn't even attempt to encode some very basic aspects of dependency. The choice you outline above is one that is not faced by most package managers, because they don't make this mistake. The naive wheel reinvention with Homebrew is so eternally disappointing, and it inevitably explains a lot of the pain users experience with it.

> Homebrew upgrades dependencies and dependents of those dependencies (which, admittedly, can feel like unrelated)

One relatively non-disruptive thing you might be able to do to make this behavior less surprising to users is (offer a way to?) print the dependency tree for package installations/upgrades that pull in upgrades of their ‘siblings’. You'd probably want to just do it in a textual way, but this project seems to model the kind of logic you'd want for printing dependency trees with Homebrew as it exists.[2]

—

1: https://github.com/Homebrew/homebrew-core/blob/master/Formul...

2: https://github.com/martido/homebrew-graph/blob/master/cmd/br...