w3m crashes. Is there a workaround?
https://trac.macports.org/search?q=w3m
If not, file one at: https://trac.macports.org/auth/login/?next=/newticket11–20 of 43 posts
w3m crashes. Is there a workaround?
https://trac.macports.org/search?q=w3m
If not, file one at: https://trac.macports.org/auth/login/?next=/newticketUpgrading 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?
Macports says they have 8199 packages. Brew has 1626 by my unscientific count (hint: $('table.tree-browser tr').length ).
A major difference is in how packages are installed. Brew by default will use native OS X packages. Macports installs all dependencies to /opt/local. So a trivial install for Brew could lead to a long install in Macports. I've had Macports build GCC.
But this new version is supposed to allow for pre-compiled binaries. So maybe a lot of that beef will disappear?
Upgrading 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?
Things I like:
* I install everything to ~/.brew/ and it works great. I did _not_ like their documented recommendation to install everything to /usr/local and chown it as your user. I have yet to run into any issues installing to my home dir.
* Installs of things have fewer deps, or at least perceived, compared to macports. Nice to not have a separate copy of everything. I haven't run into issues (yet!) where an OS update makes something puke, so this could be a problem down the road, but so far so good.
* Upgrades are very simple: brew update / brew upgrade
* Toolset is easy to work with.
* timely updates
I've been a happy homebrew user since it launched - anyone care to comment on the benefits/improvements of MacPorts V2 over homebrew?
I've gone back and forth. For a while homebrew could install a working GHC for me while I wasn't having any luck with MacPorts. Later something else caused me to switch back to MacPorts. Neither is perfect. Even MacPorts only allows dependencies at the package level, without regard to variants, or versions, if I recall correctly.
Upgrading 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?
2) Brew packages are simple to make and inspect. Many people make and inspect them. Bug fixes happen quickly.
Upgrading 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?
MacPort's package installer tools mystified me. Homebrew could be improved too, but is better.
Finally, homebrew seems more open to contributions and because they use GitHub, it's very easy to contribute new packages and the high level of activity on Homebrew reflects that. I briefly looked at what it would take to contribute to MacPorts and it was harder.
I've been a happy homebrew user since it launched - anyone care to comment on the benefits/improvements of MacPorts V2 over homebrew?
I just want it to install packages. It does that so I'm happy.
Upgrading to Lion is a great time to make the switch to Homebrew: http://mxcl.github.com/homebrew/
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.