News for hackers. Stuff that matters.
Re:Homebrew — MacPorts driving you to drink? Try Homebrew by jnoller on Saturday March 13, 2010 @01:51PM (#1189358)
I can't recommend homebrew enough - I've been burned by macports and fink in the past, and so I had reverted to the time tested "just compile stuff by hand". Homebrew strikes a good balance between the raw, do it yourself approach and something as big and intermingled as macports.
Re:Homebrew — MacPorts driving you to drink? Try Homebrew by mark_l_watson on Sunday March 14, 2010 @02:08PM (#1191019)
For years, I have "compiled stuff by hand" of OS X - not a bad approach, but it takes time. If I was just a software developer I would probably run OS X most of the time because I would have my tools built and installed once and no repeat time wasting work. For me, I also write on tech a lot, and sometimes I get some consulting work fitting people's projects to technology stacks. As a result, I have the perfect excuse to try just about everything and installing "everything" is simpler on Linux.

If Homebrew develops into a great system in the future, I might boot less to Ubuntu.

Re:Homebrew — MacPorts driving you to drink? Try Homebrew by amock on Saturday March 13, 2010 @01:59PM (#1189379)
What problems did you have with MacPorts?
Re:Homebrew — MacPorts driving you to drink? Try Homebrew by jnoller on Saturday March 13, 2010 @02:06PM (#1189394)
Frequently, when actually needing to compile other things (outside of macports), Macports would be pulled in "magically" and cause issues (such as gettext and Python-core). Frequent issues debugging strange issues when trying to port install things, etc.

Homebrew does just enough to work, and get the job done and attempts to "fit in" with the OS I already have, versus making it's own sandbox off to the side.

Re:Homebrew — MacPorts driving you to drink? Try Homebrew by amock on Saturday March 13, 2010 @02:20PM (#1189415)
The problem with accidentally pulling in libraries seems unavoidable with Homebrew since it uses /usr/local. Is the lack of sandboxing what you think makes it better? This seems like exactly what you should be looking for.

While I agree that it would be nice to have seamless integration with the OS, having a completely separate installation helps with things like OS upgrades or when you need to use a different version of a library that is installed by the OS. Does Homebrew do anything to handle that kind of problem?

Re:Homebrew — MacPorts driving you to drink? Try Homebrew by jnoller on Saturday March 13, 2010 @02:28PM (#1189427)
It can use /usr/local - and you can set it up so that /usr/local comes before the rest of your system as you need to. Yes, an entirely self-contained sandbox avoids this, but most of the time, I don't want that.

Like I said in a previous comment, most of the time I'd find myself compiling things by hand into /usr/local anyway.

Please! Use the system's provided libraries. If I need something newer, I'll brew install it myself. For me homebrew strikes a good balance between "compile it myself, damn it" and Macports/Fink. The formula are easy to hack and update (it's simple), and for the most part it just gets ourt of your way.

Re:Homebrew — MacPorts driving you to drink? Try Homebrew by jordibunster on Saturday March 13, 2010 @02:29PM (#1189430)
You don't have to use /usr/local/
Re:Homebrew — MacPorts driving you to drink? Try Homebrew by lutorm on Sunday March 14, 2010 @12:20PM (#1190821)
What problems did you have with fink?