NotRocketSurgery

Comments / Leave a response

• nukeedit
  Sheera said about 1 hour later:
  

  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.

• nukeedit
  JD said about 11 hours later:
  

  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/).

• nukeedit
  Reece said about 11 hours later:
  

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

• nukeedit
  JD said about 11 hours later:
  

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

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

• nukeedit
  Ola said 5 days later:
  

  This guy had the same problem

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

• nukeedit
  JD said 5 days later:
  

  punch.beaten_to?  #=> :always

Name	(leave url/email »)
Blog
Email
Message
Comment Markup Help