Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Homebrew was built as a source-only package manager, with the most basic of dependency management systems.

Now they try to default to binary distribution but the dependency management basically works up until compilation time only.

So for example, the Percona Toolkit package has a dependency on `:mysql` which can be provided by the Oracle mysql package, Persona Server package, or MariaDB package.

But binary packages don't really do dependencies like that - they hard-code to whatever they were built against.

The end result is you can't realistically have percona server and percona toolkit installed via homebrew, without also having the oracle mysql package installed and constantly link/unlink-ing between percona server and oracle mysql whenever you need to update percona toolkit.

Do you know what the Homebrew response to this issue was?

Close the issues, remove/disable the binary package of percona-toolkit, and force all users to compile the package from source, every time they install/upgrade it.

To even put Homebrew in the same category of tools as Apt/Dpkg or Yum/RPM is a joke.



Are we talking about apt on Debian/Ubuntu vs Homebrew on Mac or about some special Mac apt?


The only apt I know is the Debian package management tool.


Ah, my bad, I misread earlier and thought you meant homebrew was better than apt.

Sorry. My fault.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: