Installing wget took about 20 seconds... brilliant.
Homebrew — MacPorts driving you to drink? Try Homebrew
41–50 of 65 posts
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#42I currently use MacPorts... just wondering why I should switch?
FWIW, I was an early Homebrew user and even contributed a few recipes, but I moved back to MacPorts because (and no offense to mxcl, but it's kind of unavoidable) the author seems to do things with little understanding of the underlying system or justification. Taking ownership of /user/local is completely utterly pointless and just plain bad advice. Copy-and-pasting optimization code from the Gentoo wiki is pointles…
I really wanted to keep liking Macports, but I got sick of having to install a new perl just to install git, among many examples. The kicker for me was installing pandoc; Macports wanted to download and compile a new GHC, refusing to recognize the one on my system. I let it run for 3 hours and finally killed the install and looked for a better way to do things.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#43I currently use MacPorts... just wondering why I should switch?
FWIW, I was an early Homebrew user and even contributed a few recipes, but I moved back to MacPorts because (and no offense to mxcl, but it's kind of unavoidable) the author seems to do things with little understanding of the underlying system or justification. Taking ownership of /user/local is completely utterly pointless and just plain bad advice. Copy-and-pasting optimization code from the Gentoo wiki is pointles…
It seems the anti-homebrew complaints basically amount to "I don't understand this, so I'm going to say it's bad".
The biggest reason I've seen to get rid of Macports in favor of Homebrew is software versions, Homebrew is constantly up to date and I can upgrade software with ease. Not so with Macports.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#44this is #1 what drives me nuts about macports: $ port deps clojure-contrib Full Name: clojure-contrib @1.1.0 Build Dependencies: clojure Fetch Dependencies: git-core $ port deps git-core Full Name: git-core @1.7.0.2+doc Runtime Dependencies: rsync, perl5, p5-error Library Dependencies: curl, zlib, openssl, expat, libiconv with no possibility of skipping dependencies
Poor package management isn't the fault of MacPorts; a Homebrew port could be just as poorly designed.
The "variants" infrastructure of MacPorts is one of my favorite parts of MacPorts, it definitely makes it easier to manage interdependencies IMHO.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#45I currently use MacPorts... just wondering why I should switch?
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#46I currently use MacPorts... just wondering why I should switch?
FWIW, I was an early Homebrew user and even contributed a few recipes, but I moved back to MacPorts because (and no offense to mxcl, but it's kind of unavoidable) the author seems to do things with little understanding of the underlying system or justification. Taking ownership of /user/local is completely utterly pointless and just plain bad advice. Copy-and-pasting optimization code from the Gentoo wiki is pointles…
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#47Earlier quoted context omitted.
FWIW, I was an early Homebrew user and even contributed a few recipes, but I moved back to MacPorts because (and no offense to mxcl, but it's kind of unavoidable) the author seems to do things with little understanding of the underlying system or justification. Taking ownership of /user/local is completely utterly pointless and just plain bad advice. Copy-and-pasting optimization code from the Gentoo wiki is pointles…
Just a side note but /usr does not actually stand for /user (although I often pronounce it that way when speaking). It's actually an initialism standing for UNIX System Resources.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#48Earlier quoted context omitted.
I haven't switched to Homebrew but the advantage is that MacPorts creates its own universe of libraries, whereas Homebrew uses what Mac OS X already comes with. This makes installs a lot faster.
MacPorts creates it's own universe because that's the only reliable way to do it. What will Homebrew do when Python gets updated by Apple, or when you want 2.6.10 and Apple only has 2.6.4? With Macports the situation is easily dealt with, with Homebrew it's not.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#49I use MacPorts, and I've used a bunch of various package management systems, and portage is the only one that lets me maintain servers for > 5 years without reinstalling the whole thing, just upgrading the packages.
Re: Homebrew — MacPorts driving you to drink? Try Homebrew
#50Earlier quoted context omitted.
Did ubuntu suddenly get TextMate support? Also, have they fixed the poor graphics acceleration issues? Didn't think so, go away troll.
That's cool if you're happy with OS X. It's just that I know many OS X devs who use ubuntu in a VM. I'm personally happy with a full install of Ubuntu and Emacs instead of textmate while others prefer OS X + textmate or emacs or vim or what have you, to each his/her own. I was just stating an alternative, I didn't know that was trolling.
I'm very suspicious of your story.