An open-source community system for compiling, installing, and upgrading command-line, X11 or Aqua based open-source software on OS X.
Ranked in these QuestionsQuestion Ranking
Pro Provides a consistent experience across OS X versions
MacPorts eschews Apple-supplied libraries and links sources against its own making sure that the experience is the same regardless of what OS X version is used.
Pro Nice variants system
MacPorts has a variants system that allows customizing builds with author provided options.
Pro Generally very up to date
MacPorts generally gets new software soon after it's available. This way users will not have to worry if their software is up to date.
Written in Tcl & C, it's generally significantly faster than the competition. Tcl is also quite readable and comparable to Ruby, so it's also friendly to newcomers.
Pro Requires SUDO to install apps
No need to worry if some rogue app will change your binaries or configuration.
Pro Has many more packages than its competitors
As of this writing, 20K packages. 3 to 5x more than other current package managers.
Pro MacPorts is a native application: C + TCL
No need to install Ruby, or any other programming language.
Pro Most of the available packages work
For example, trying to install Finch using Pkgsrc doesn't work, while installing it using MacPorts works perfectly. Finch isn't even on Homebrew's radar.
Con Bad at limiting dependencies
MacPorts has a habit of pulling very specific versions of dependencies for each package. It downloads different version of already existing dependencies even in cases where the existing dependency version would have worked seamlessly.
Con Downloads unneeded libraries duplicating functionality already provided by Apple's libraries
As MacPorts eschews Apple-supplied libraries and links sources against its own a large duplication of functionality across MacPorts and Apple libraries can be found.