Stuff that comes with OS X or is a library that is provided by We really don’t like dupes in Homebrew/homebrew It will also use as many of the local libraries that are available in OS X. Homebrew will warn you when you should install things "natively" (using the library/tool's preferred installer) for better compatibility. Perhaps I should clarify - I did not say anywhere in my answer that macports overwrites OSX native packages. Packages? As far as I can tell, all macports installation happens in Need to be certain of what you are using and Apple's change atĭifferent times to the ports and have been know to be years behindĬan you give a reference showing that macports overwrites native OS X Version - This is the main reason I prefer macports over home-brew, you Macports does not overwrite native OSX packages - it supplies its own Homebrew also enjoys a more active user community and its packages (called formulas) are updated quite often. This helps when getting rid of libraries as well since everything is in a path accessible to you. It also installs libraries in the user space (thus, you don't need to use "sudo" to install things). This means that if there is a native package available, homebrew will notify you instead of overwriting it and causing problems further down the line. One major difference between homebrew and macports and the reason I prefer homebrew is that it will not overwrite things that should be installed "natively" in osx. For anyone familiar with any of the BSD distributions, macports will feel right at home. Macports is an osx version of the port utility from BSD (as osx is derived from BSD, this was a natural choice). Xcode can be installed from the mac app store, its a free download but it takes a while since its around 5GB (if I remember correctly). They both need the xcode command line tools installed (which you can download separately from ), and for some specific packages you will need the entire xcode IDE installed. Typically these are development related libraries and the most common use of these tools is for developers working on osx. Homebrew and macports both solve the same problem - that is the installation of common libraries and utilities that are not bundled with osx. Rubists like to rewrite everything in Ruby, because the only thing they are at ease is Ruby itself. All the relative extensions are part of the group and they will be activated within the chosen group: php55 or php56. If you have both PHP55 and PHP56 installed (with many different extensions), you can swap between them with just one command. Python none python24 python25-apple python26-apple python27 python27-apple none Postgresql postgresql94 postgresql93 postgresql94 none If you are a PHP developer you can install the last version of Apache (Mac OS X uses 2.2), PHP and all the extensions you need, then upgrade all with one command. MacPorts is really stable, in 8 years I never had a problem with it, and my entire Unix ecosystem relay on it. To install Ruby on Mac OS X you might need MacPorts, so just go with MacPorts and you'll be happy. MacPorts is a native application: C + TCL. With brew you'll find yourself trapped soon because the formula you need doesn't exist. Like pointed, MacPorts has many many more packages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |