Then you spend a bit looking for other references to see if the one you're following is the new way or the old way that won't work right anymore. It starts with finding some random blog post on Google that differs from every other blog post on Google about how to accomplish the install. Python, PHP, OpenJDK are ones that I've specifically had issues with. Not to mention that the recommended way of installing certain packages changes seemingly randomly sometimes. The big thing that made that preferable is that the services (databases and such) are not run on the bare machine but rather in containers. They solve problems in different ways and have different repercussions for how users use them.įor me, on my systems, I've found that I tend to prefer to fix the problems that Homebrew causes than the problems that MacPorts causes. I believe that both Homebrew and MacPorts have made design choices that reflect how they want to take their respective projects and I respect those design choices. That's a "my experience" story and isn't meant to be defining. I had an issue with MacPorts many years ago when I was trying to install a python library via MacPorts (I forget exactly why) but wasn't being found with python on the command line (which was using the system toolchain) and then when I resolved the "I'm using the MacPorts version on the command line" other issues with software that was expecting the system toolchain version started cropping up. but the issue in the MacPorts toolchain remains until that is updated. Apple pushes out a security update that updates the system toolchain. (making up a story here) there's a vulnerability found in Ruby which is part of the toolchain for the system and in MacPorts toolchain. The spot where this becomes an issue would be say. Printf "%s\n" flip side of that is "do you want to have two scripting and compiler toolchains installed on the machine - one that gets updates from the vendor and one that gets updates from volunteers?" Share/man/man5 share/man/man6 share/man/man7 share/man/man8 Share/man/man1 share/man/man2 share/man/man3 share/man/man4 Share/aclocal share/doc share/info share/locale share/man # On Intel macOS, this script installs to /usr/local onlyĭirectories=(bin etc include lib sbin share opt var To install elsewhere (which is unsupported) ![]() This matches how my current Mac, which has brew, is currently setup as well. If I read homebrew's install.sh correctly, it changes ownership of a few directories under /usr/local, not /usr/local itself (on x86, on ARM it follows a different path). Homebrew wants you to change ownership of /usr/local to your individual user
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |