![]() This means that a) other user accounts on the system can't easily install or manage packages, and b) any process running as the owning user account can make changes to its files. Its directory hierarchy is not owned by root. ![]() That is completely unacceptable for a package manager! It is failing at its one job. I can't count the number of times I'd upgrade a package, or install a new package which would automatically upgrade other packages in order to meet its dependencies, and then find that many of my existing packages were now broken. It constantly breaks dependencies when upgrading packages. Gonna have to disagree here! Homebrew is a very troublesome package manager, and anyone who has experience with other package managers (which mainly means folks who are experienced with Linux) will probably see its flaws and issues pretty quickly.Īfter using Homebrew for years and getting frustrated with its shortcomings, I finally made the switch to MacPorts and have never looked back. A formula can mark itself as auto_updates for apps that push updates themselves, but if the app doesn't push updates then homebrew isn't going to update it for you. That's on whoever wrote the cask formula. envrc file in the project root to set things like PATH and GOROOT appropriately. For example, I have a project that builds with Go 1.18 so I installed and have an. For these cases I tend to rely on direnv. Otherwise you can fork the formula and use that.Īlso I miss an easy switch between versions and variants if I install a few versions of a tool. brew install -git could also be useful if you need to patch things. I personally don’t like (mostly) lack of build options while installing a package.īrew install -interactive might help. PS: I understand where Homebrew may be slightly better, but issues above are crucial for me With all of this, I have Homebrew in a it’s own custom folder, and not in PATH (as I don’t need most tools installed by it). I can install a newer version by uninstalling and installing it back, but I prefer to have some automation. I don’t know the reason of this action, but it’s frustrating for me.Īlso I surprisingly found, that when I’m installing a binary proprietary application (like an IDE or something) I have no updates. Also I miss an easy switch between versions and variants if I install a few versions of a tool.Īlso I prefer never to install a library to /usr/lib, as Homebrew does with libs like libz. I personally don’t like (mostly) lack of build options while installing a package. I prefer MacPorts for the most ports and Homebrew for (mostly) fonts. Otherwise, it’s my personal pain to use 2 package systems at once. If you have a way how to fix that, I can change it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |