Upgrading to Lion is a great time to make the switch to Homebrew: http://mxcl.github.com/homebrew/
Giving this a try now. While I'm waiting for XCode to download, can anyone comment on the best way to get Apache httpd running on OSX? Is there a Homebrew package for this? I use Apache to front Tomcat on a linux server, but it would be really handy to be able to test stuff locally on my Mac before copying changes up to the server.
MacPorts 2.0 with Lion support now available
21–30 of 43 posts
Re: MacPorts 2.0 with Lion support now available
#22Earlier quoted context omitted.
Giving this a try now. While I'm waiting for XCode to download, can anyone comment on the best way to get Apache httpd running on OSX? Is there a Homebrew package for this? I use Apache to front Tomcat on a linux server, but it would be really handy to be able to test stuff locally on my Mac before copying changes up to the server.
Im not sure about Lion, but OSX comes with built in apache server. Goto System Preferences > Sharing > Web Sharing
Re: MacPorts 2.0 with Lion support now available
#23Upgrading to Lion is a great time to make the switch to Homebrew: http://mxcl.github.com/homebrew/
Benefits over MacPorts? Which has more up-to-date packages?
Re: MacPorts 2.0 with Lion support now available
#24MacPorts has been annoying since day one, but it worked where there was nothing else truly competitive (Fink? Everything bad in MP, plus even slower updates. Only benefit is the sometimes-functional binary installs). Now we have Homebrew, and it's way better, if it has fewer legacy recipes (though not always).
Re: MacPorts 2.0 with Lion support now available
#25After "debugging"-it, e.g: port -v self update
it gave me some mysterious problem of SQLite missing 64-bit version from... /Library/Mono.Framework/.../sqlite.dylib - don't remember the details.
Found some notes how to uninstall mono from their site (little script), and then "port selfupdate" went fine.
Re: MacPorts 2.0 with Lion support now available
#26Upgrading to Lion is a great time to make the switch to Homebrew: http://mxcl.github.com/homebrew/
Benefits over MacPorts? Which has more up-to-date packages?
Homebrew tends to have fresher packages---new versions of popular packages are usually updated within hours.
Haven't look back to MacPorts since switched to Homebrew two years ago.
Re: MacPorts 2.0 with Lion support now available
#27I've been a happy homebrew user since it launched - anyone care to comment on the benefits/improvements of MacPorts V2 over homebrew?
Last time I looked, MacPorts had a more paranoid approach to dependencies. That can be good and bad. Homebrew can be easier to use, until you run into a corner case that trips it up. MacPorts can be frustrating in how many dependencies it will insist on installing its own version even though the system-provided version might have worked. I've gone back and forth. For a while homebrew could install a working GHC for m…
Re: MacPorts 2.0 with Lion support now available
#28Earlier quoted context omitted.
Benefits over MacPorts? Which has more up-to-date packages?
Brew doesn't install the whole universe and take hours to install a small utility. MacPorts does.
Re: MacPorts 2.0 with Lion support now available
#29Earlier quoted context omitted.
Benefits over MacPorts? Which has more up-to-date packages?
1) Brew doesn't hide my stuff in /opt/macports/opt/package/ports/port/python/etc/etc/etc 2) Brew packages are simple to make and inspect. Many people make and inspect them. Bug fixes happen quickly.
I actively create patches and submit it to them whenever I run into a problem, and I will keep doing so, because it's typically only a few days until it gets merged.
How I got into it, was the nifty searching of Github issues that Homebrew does for existing issues when you have a compilation error. One way to get people to report bugs is to show them you care..
Re: MacPorts 2.0 with Lion support now available
#30Earlier quoted context omitted.
Brew doesn't install the whole universe and take hours to install a small utility. MacPorts does.
Does brew compile from source? That is one of the most frustrating aspects of macports, for example I was trying to install a simple musical ear training tool the other day and it went to compile GCC. Argh!