On Fri, Jul 1, 2011 at 12:09 AM, Brian Aker <br...@tangent.org> wrote: >> I think that is mostly a product of the poor mysql build story. There >> was a time where building mysql was dark black magic, and often caused >> deep issues for people. The binary tarball was more supportable for mysql. > > At one point there was a lot of bugs in libc/etc. Shipping binaries was the > only way to get a stable copy of MySQL. > > Today though? I would think it would be less problematic.
The common use cases for using tar binaries today are - surprisingly many just like to install mysql in /usr/local/mysql as their primary method. - in particular this allows them to keep many installations lying in /usr/local/, switching between them with a symlink. With Deb/Rpm you can only keep one version installed. - I assume I can install Drizzle alongside MySQL, but for the other forks it's also an issue that people want to try out new versions while also keeping the official MySQL 5.1 that came with the distro. The same will be true for Drizzle: People want to keep the old version installed while trying out newer releases or beta releases. I don't feel strongly about this, just providing feedback. henrik -- henrik.i...@avoinelama.fi +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
