(For the same reasons, fink uses /sw as its prefix. MacPorts doesn't want to be a victim of that, and /opt/local provides the splendid isolation (as would any other dedicated directory, of course).Īlso, /usr/local traditionally contains the given system's local admin tools MacPorts doesn't want to stomp on that either. While this could be dismissed as the user's own error, it is a fact that people click through installers blindly, and consequently collisions under /usr/local (and other prominent directories) happen very often. Many other software packages and packaging systems install into /usr/local, and could accidentally overwrite what MacPorts has installed, or vice versa. However, having MacPorts under /usr/local would be error-prone for precisely that reason. Traditionally, the place to install third party software on many UNIX systems is /usr/local. MacPorts is a powerful command-line tool for installing and updating a variety of. Why is /opt/local the default install location for MacPorts? PortAuthority provides a graphical user interface for the MacPorts package management system for Mac OS X. PS: This article I found on the subject raises some good other points. If you don't know what the fuck I'm talking about, use Homebrew. If it bothers you when your bash and perl scripts don't work the same on Mac, use MacPorts. If your primary/only programming language is JavaScript, Python, or Ruby, Homebrew. If you use the command line only to manually type and execute short sequences of commands: Homebew. If you write scripts / software that you run in the command line, MacPorts. If you think Oh My Zsh is slow bloatware, go with MacPorts. ![]() If you like Oh My Zsh, you're probably a Homebrew user. MacPorts may be conceptually divided into two main parts: the infrastructure, known as MacPorts base, and the set of available ports. If you prefer CamelCase and terms like x-ly, x-ify, x-io, and x.js, Homebrew is probably better for you. MacPorts is an easy to use system for compiling, installing, and managing open source software. if you like short, all-lowercase words like awk, sed, grep, vim, and gcc, MacPorts. ![]() Every time I've tried with Homebrew, something eventually goes horribly wrong. It's fine to try to hide the details from the user until something goes wrong. Homebrew wants to be Mac-like in its easiness, but I prefer transparency over a veneer of simplicity. If youre trying to use multiple package managers to maintain. Ive run into very few difficulties this way, even before learning the port -t trick. I think Homebrew is great for people who don't typically use the command line but absolutely need to install one piece of command line software for a project, or for people who use the command line frequently, but mostly only to `npm run build` and `git push`. To be honest, I run with Fink, MacPorts and Homebrew all at once, with deference to MacPorts (for now anyway), and only using either of the other two to install things I cant get from MacPorts. I also use my Mac to administer a number of Linux servers. I'm a software engineer and spend almost all of my computer time in a fullscreen terminal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |