One issue is that the MacPorts built versions of things don't always integrate in a nice way with other parts of the system.
I realize this is anecdotal, but my experience has been much more like robbles' than mapgrep's. (And I know that's harsh but for a long time they trashed Macports right in their tagline - "Is MacPorts driving you to drink?" - which just seemed gratuitous.) My bias here is that I'm a longtime happy Macports user who has tried to use homebrew repeatedly, encountered lots of failed recipes, and gone back to Macports, shaking my head at all the hype around homebrew and the fact that is has somehow become a defacto developer default despite some really sloppy, poorly thought through practices. But you don't get key components changing out from underneath your packages due to an Apple System Update.
Macports el capitan install#
Macports really only depends on a slice of Xcode from time to time updates will fail to install until you open Xcode and accept whatever new license Apple has bundled with it. But then it is much more fragile when your system updates. Homebrew offers a much faster initial install because it leans on OS X libraries for various things. The downside is that it takes forever to install the first few packages. Macports just has a much more robust philosophy of building its own universe largely separate from OS X, and only rarely impacted by system updates. Macports, meanwhile, continues to work quite well because it 1.
0 kommentar(er)
