![]() ![]() ![]() As a consequence they've tended to be fairly comprehensive stacks, often duplicating system provided software which have been a source of issues. several common libraries were installed as frameworks). Fink and (a little later) MacPorts date from a time when OS X was a pretty eccentric unix (e.g. My notes on working with MacPorts are here.Īll these projects solve the same problem: provide package management on a third party OS. I am willing to bet that there are cases where Homebrew or Fink are better than MacPorts. Fortunately, a wiser person than me pointed me (back) to MacPorts.Īll that noted, like many things, it all depends on what software / functionality you are trying to manage with one of the three. I generally prefer Homebrew, but I have found that in my particular case, working with Python, MacPorts excels at making everything "just work." I fought and fought to get SciPy and Numpy and the NLTK up and running on my Mac using Homebrew, but it just wasn't happening. One of the greatest strengths of such systems is that they can often manage various dependencies for you, and essentially say to you, "Hey, you are about to install X, did you know you will need Y to make that work? You wanna install that too?" I'm guessing from your question you already have a general sense of a package management system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |