NotRocketSurgery: MySQL Version Hell

MySQL Version Hell

jd — Sat, 28 Oct 2006 02:27:00 -0400

This article has moved over to our sister spin-off blog, RubyJudo, which focuses on more arcane technical topics than NotRocketSurgery.

"MySQL Version Hell" by JD

Wed, 01 Nov 2006 20:07:25 -0500

punch.beaten_to?  #=> :always

"MySQL Version Hell" by Ola

Wed, 01 Nov 2006 13:52:42 -0500

This guy had the same problem

http://www.railtie.net/articles/2006/09/12/running-rails-on-os-x-with-mysql-5-0-24

"MySQL Version Hell" by JD

Sat, 28 Oct 2006 13:25:10 -0400

> Since it’s not an application, AppZapper does not work.

Maybe I’m wrong, but I couldn’t get AppZapper to do anything useful.

"MySQL Version Hell" by Reece

Sat, 28 Oct 2006 13:04:12 -0400

I’d suggest looking at AppZapper. It does a pretty good job of taking care of such things during an uninstall. http://appzapper.com

"MySQL Version Hell" by JD

Sat, 28 Oct 2006 13:00:23 -0400

I was using the pre-built OS X packages, not compiling from source. From my experience, installing mysql using MacPorts is not ideal, mostly because it won’t start on startup and you have to run it manually. If you install the OS X package you get a preference pane and a startup item. Normally, it all works out for the better.

I could have just done sudo rm -r /usr/local/mysql to remove the pre-built package, but that isn’t the “right way” to remove an installed package incase it put something somewhere else (e.g., /Library/Receipts/).

"MySQL Version Hell" by Sheera

Sat, 28 Oct 2006 03:34:59 -0400

Forgive my ignoreance

But why do we need uninstallers?

If compiling from source, isn’t it easy enough to manually remove the appropriate directories from /usr/local ?

I’ve always wondered what the advantages are to packages and installers.