MySQL Bugs: #1526: libmysqlclient.so.10 dep

Bug #1526	libmysqlclient.so.10 dep
Submitted:	10 Oct 2003 16:12	Modified:	19 Nov 2003 5:15
Reporter:	lance Vavricka	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	4.x	OS:	Linux (Linux (Intel))
Assigned to:	Lenz Grimmer	CPU Architecture:	Any

Description:
I hope the final release will be hassle free for upgrading.  Some of us don't have the luxury of taking the time to recompile everything dependant on libmysqlclient.so.10, atleast not in a production environment.  There's no way I can take down a few of these things to recompile just to upgrade mysql.  Not really a bug but MySQL should be backwards compatiable for libraries, I'd have to recompile just about every daemon.

How to repeat:
upgrade from 3.23 to 4.x, easy huh?

Suggested fix:
backwards compatibility for libmysqlclient.so.10 so other programs don't break.

LenZ any comments ?

Let me quote from our manual (http://www.mysql.com/doc/en/Linux-RPM.html):

"If you get a dependency failure when trying to install the MySQL 4.0 packages (for example, ``error: removing these packages would break dependencies: libmysqlclient.so.10 is needed by ...''), you should also install the package MySQL-shared-compat, which includes both the shared libraries for backward compatibility (libmysqlclient.so.12 for MySQL 4.0 and libmysqlclient.so.10 for MySQL 3.23).

Many Linux distributions still ship with MySQL 3.23 and they usually link applications dynamically to save disk space. If these shared libraries are in a separate package (for example, MySQL-shared), it is sufficient to simply leave this package installed and just upgrade the MySQL server and client packages (which are statically linked and do not depend on the shared libraries). For distributions that include the shared libraries in the same package as the MySQL server (for example, Red Hat Linux), you could either install our 3.23 MySQL-shared RPM, or use the MySQL-shared-compat package instead."