1/30/2024 0 Comments Install homebrew for mac m1For example on my M1 system I would require two homebrew installs one for Intel and another for arm64.\įor Intel installs it takes over /usr/local, that’s not always a good thing. If any upstream package is broken homebrew won’t attempt to fix it themselves and will instead ship it as is, unless an upstream patch is available. Now Homebrew is officially available for ARM64 Mac M1 computers, you can easily install on your Mac, and with the help of Homebrew you can build the packages from source code into ARM64 executable. Homebrew, only supports the current versions of macOS that Apple still supports, constantly updated to the latest packages, the “cask” system making installing some software way simpler. Macports by default installs to /opt/local and always requires sudo for installs. But it’s possible to build package with more than one architecture.\ Macports is usually much more stable and supports as many versions of macOS as possible, if something upstream is broken Macports will attempt to fix the issue, ports won’t always be the latest version. I use both Homebrew and macport actively for different systems. I think Apple wouldn't like to add a package manager themselves because terminal programs are not the thing most of the people would like to use (having UI is always better), but they care about the existing package managers, as they were saying they would help with porting brew and macports on m1 along with other projects (WWDC2020) ![]() Macports uses /opt/local, homebrew on m1 uses /opt/homebrew, so by cleaning these folders you can get rid of them easily if you are not satisfied. ![]() If everything was already recompiled, I would say both managers are great, so you can pretty much try both and decide for yourself. Also I prefer the way Python is distributed, compared to macports, where you have to delete the previous version and install the next version each time it has major update (because all formulas are named differently). Homebrew is adapting really quickly, it already has gcc10 for m1 (which is not officially supported, but people created custom build just to use until gcc11 is out) and many other native compiled tools which are not easy to build from source and are not on macports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |