Someone needs to write some nice blog entries on using Homebrew and link them from here
- From:
- sojourner
- Date:
- 2010-07-12 @ 05:03
Gathered some links for you. Not creating an account to edit your wiki.
Format:
Title
Snippet
URL
Homebrew is the new macports
Yeah, you heard me! I’ve made the switch and so should you! Or, you
don’t have to, but it is a really sweet and simple solution for
dealing with packages for Mac OS X.
http://sofaware.org/post/390985249/homebrew-is-the-new-macports
MacPorts to Homebrew : New Packaging system for Mac OS X
I just wanted to blogpost this only because, I started loving Homebrew
– the new package management system for Mac OS X wich beats MacPorts.
And Homebrew is faster.
http://abhinay.wordpress.com/2010/01/02/macports-to-homebrew-new-packaging-system-for-mac-os-x/
The philosophy of Homebrew is radically different from MacPorts or Fink.
Homebrew tries to work as far as possible with the pre-installed big
items (Perl, Ruby, Python). It drags in as few dependencies as
possible, in general, from what I can tell. Both Fink and MacPorts, on
the other hand, install virtually an entire second world of software -
parallel to the built-in Apple stuff - in their respective sub-
directories (/sw for Fink and /opt/local for MacPorts).
http://news.ycombinator.com/item?id=840428
Alternative to MacPorts, homebrew
If you’ve ever needed a 3th party app like wget or anything like it
you should probably take a look at homebrew. Its fast and slick and
bound to git. It has all the great features we know from apt
ormacports. What more could we ask for? Some of the things ive used it
for the last couple of days is installing and playing with nginx which
is an awesome tiny webserver that has a brilliant json like syntax for
vhosts.
http://christiank.org/wp/2010/03/alternative-to-macports-homebrew/
Homebrew, the perfect gift for command line lovers
My favorite thing about Homebrew is its ability to function perfectly
well with /usr/local as its base directory, installing packages in
their own folders but linking them to /usr/local/command. This makes
them manageable with existing command line tools. Homebrew can work
out of any directory you like, if /usr/local isn't your cup of tea.
Installed packages are optimized and stripped based on your
architecture, and makes great use of libraries you already have
installed or that came with the system, reducing duplication and
speeding up download, compile and install times significantly. Add in
the zero-config installation, an already-extensive list of
"formulas" (packages), a greatly-reduced need to sudo anything, and a
Ruby-based framework for creating your own formulae and you've got a
killer package for extending your command line toolset.
http://www.tuaw.com/2009/12/25/homebrew-the-perfect-gift-for-command-line-lovers/