Re:2009 Rubyist's guide to a Mac OS X development environment
by gcv on Tuesday March 31, 2009 @05:46PM
(#540904)
Indeed. MacPorts has the additional advantage of using upgradable and removable packages, rather than polluting /usr/local (or worse, /usr) with unmaintainable detritus of various .pkg installers. MacPorts packages do occasionally fail to build, but (1) the maintainers do respond to tickets opened in their Trac system, and (2) most problems I saw had to do with Python packages, and MacPorts handling of Python apps seems to have improved recently.
Re:2009 Rubyist's guide to a Mac OS X development environment
by YuriNiyazov on Thursday April 02, 2009 @09:11PM
(#544315)
Indeed, I now have a new rule: MacPorts provides everything I need except for Ruby and Python, which are always compiled from source into a separate location where they can pollute all they want.
Re:2009 Rubyist's guide to a Mac OS X development environment
by hbien on Tuesday March 31, 2009 @05:23PM
(#540864)
For me, it's b/c of the bad experiences I had with it. Packages never compiled correctly, I always got error messages which I'd google around for. It would take over an hour to finally install MySQL, Subversion, SQLite3, etc...
I must be an idiot if I can't do 'sudo port install PACKAGE' correctly.
Then I got a new laptop and just used the .pkg installer, way easier and faster.
Git: sudo port install git-core
Aliases: do not want. sudo port install bash-completion
MySQL: sudo port install mysql5 +server
Capistrano: sudo gem install vlad
ImageMagick: sudo port...
Quicksilver: out with the old, in with http://code.google.com/p/qsb-mac/
I don't get the anti-macports attitude. Why go through the hassle of downloading a bunch of stuff when it can be just a command line away?