3 ms·

I just want to add, that once you want packages and such, for a tool chain, you'll at least discover some problems, as there is a package anarchy out there com

by McUsr 14y ago

I just want to add, that once you want packages and such, for a tool chain, you'll at least discover some problems, as there is a package anarchy out there compared to GNU/Linux! But http://macports.org http://macports.org has a solid repository of packages. When it comes to "private packages" packages I have found outside repos, I do install them as "account installs", that is ~/opt/bin, ~/opt/man/man1 .. and so on, so it is easier to upgrade the OS, and less conflicts with the different packet managers. Having said that, most things do work, and people are friendly and easy to reach. Most GNU packages just work, shouldn't you find what you are looking for elsewhere. I think Mac Os X, (or just OS X now adays), is the greatest platform for free software ever! My reason for starting out with a Mac was Applescript (http://macscripter.net http://macscripter.net) and inter application communication IPC. I haven't regretted that a single day.

chimeracoder 14y ago
> But http://macports.org http://macports.org has a solid repository of packages. The problem comes when you start wanting to use things that aren't on Macports, and are only on homebrew (or maybe fink). But homebrew won't work with macports! So either you have to install one package or the other manually, or you have to install both macports and homebrew, which means that not only are you dealing with an unsupported setup, but you're also dealing with using two separate package managers for the same operating system. Oh, and don't forget that anything installed via the App Store is completely independent of all of the above. As a Linux user, I find this concept mind-boggling. I don't have time to keep track of a thousand different package managers. I just want one that handles everything.
- lucian1900 14y ago
  I've found that with Homebrew's very simple recipes, you can find one for pretty much anything. I've been satisfied with some binary vendor-provided packages + app store + homebrew for everything else.
- simonh 14y ago
  I use the same solution as Miguel. Linux under VirtualBox. So in fact every Mac I've ever owned has also been a Linux machine too. In fact, sometimes several Linux machines!
- xentronium 14y ago
  It's not that hard, really. You install libraries and console stuff from homebrew, gui applications from app store and forget about macports.
  - McUsr 14y ago
    I'd say the opposite, forget about Homebrew and keep Macports. The whole thing may not be so easy to use at first, but when you have read the docs for the port system, it all makes much more sense.

by McUsr 14y ago

chimeracoder 14y ago

> But http://macports.org http://macports.org has a solid repository of packages. The problem comes when you start wanting to use things that aren't on Macports, and are only on homebrew (or maybe fink). But homebrew won't work with macports! So either you have to install one package or the other manually, or you have to install both macports and homebrew, which means that not only are you dealing with an unsupported setup, but you're also dealing with using two separate package managers for the same operating system. Oh, and don't forget that anything installed via the App Store is completely independent of all of the above. As a Linux user, I find this concept mind-boggling. I don't have time to keep track of a thousand different package managers. I just want one that handles everything.

lucian1900 14y ago
I've found that with Homebrew's very simple recipes, you can find one for pretty much anything. I've been satisfied with some binary vendor-provided packages + app store + homebrew for everything else.
simonh 14y ago
I use the same solution as Miguel. Linux under VirtualBox. So in fact every Mac I've ever owned has also been a Linux machine too. In fact, sometimes several Linux machines!
xentronium 14y ago
It's not that hard, really. You install libraries and console stuff from homebrew, gui applications from app store and forget about macports.
- McUsr 14y ago
  I'd say the opposite, forget about Homebrew and keep Macports. The whole thing may not be so easy to use at first, but when you have read the docs for the port system, it all makes much more sense.