MySQL Bugs: #474: libmysqlclient.so.10 upgrade from 3.2 to 4.1

Bug #474	libmysqlclient.so.10 upgrade from 3.2 to 4.1
Submitted:	21 May 2003 9:28	Modified:	26 May 2003 2:56
Reporter:	test test2	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	RH 8.0	OS:	Linux (Linux)
Assigned to:	Lenz Grimmer	CPU Architecture:	Any

Description:
I am still using 3.2 and was would like to upgrade to 4.1. The install instructions for 4.0 recommend that you first upgrade to from 3.2 to 4.0, then 4.1. I am running PHP, Perl and MyODBC and pre bug report #348 this issue has yet to be resolved. 

Issue:
"Upgrading to 4.0 MySQL may not be possible if you run PHP, Perl or MyODBC.... At this time, most rpm's and packages have a dependency on libmysqlclient.so.10, instead of libmysqlclient.so or libmysqlclient.so.12. This does not occur in every case since the linkage process differs with different build strategies. If you have this difficulty may wish to file a bug "http://www.mysql.com/doc/en/Bug_reports.html report" as well as the particular 3rd party vendor/packager and request that the 3rd party upgrade thier package linkage for libmysqlclient.so. Any strategies for short term work arounds would be helpful."

- Has this lib issue been resolved?
- Is there new installation documentation avalible somewhere that allows a version jump?

If this issue is not resolved, it will be interesting to see how users are to jump from 3.2 to 5.0 here in the near furture.

How to repeat:

For MySQL 4.0.13, we now also provide a new RPM "MySQL-shared-compat" 
(see http://www.mysql.com/doc/en/Linux-RPM.html) - does this resolve the problem for you?

Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 
http://www.mysql.com/downloads/

Providing the MySQL-shared-compat package seems to have resolved this issue for the time being.