MySQL Bugs: #52683: conflicts of libmysqlclient

Bug #52683	conflicts of libmysqlclient
Submitted:	8 Apr 2010 9:13	Modified:	13 Apr 2010 16:04
Reporter:	Susanne Ebrecht	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:		OS:	Any (Linux, Mac)
Assigned to:		CPU Architecture:	Any

Description:
This is related to bug #52682

This is a package problem for Linux and Mac:

MySQL 5.0 is using libmysqlclient15.
MySQL 5.1 is using libmysqlclient16.

Workbench says it needs minimum libmysqlclient15.

What if installed libmysqlclient is older then 15?
Means < 15.

Workbench is not allowed to overwrite old versions without
letting the user know about it.

A simple solution could be to:
When version is < 15
Then stop installation and plead the user to upgrade client.

What if installed libmysqlclient is younger then 15?
When version is > 16

Of course libmysqlclient16 or higher should be taken.
No need to install the older version.

What if both libmysqlclient15 and libmysqlclient 16 is installed?
Then libmysqlclient16 should be taken because libmysqlclient15 is not
supporting all features from server 5.1.

What if installed libmysqlclient == 15?
This could get problems when user is using it with server 5.1.

At the moment we have to deal with 6 and more combinations here:
client 16 + server 5.0
client 16 + server 5.1
client 16 + server higher 5.1
client 15 + server 5.0
client 15 + server 5.1
client 15 + server higher 5.1

client older or younger + server x.y.

Solution Result:
When libmysqlclient is < 15
Then
Stop installation and plead user to install libmysqlclient16.

Because then we can be sure that always and only libmysqlclient16 is taken and we just have three combination:

client16 + server 5.0
client16 + server 5.1
client16 + server higher 5.1

How to repeat:
...

Suggested fix:
See above

Aargs typo ... of course I meant:

Solution Result:
When libmysqlclient is < 16
Then
Stop installation and plead user to install libmysqlclient16.

Windows and Mac bundle the client lib. We already checked the correct version is being used as part of bug #52682

Linux packaging systems already do version checking, if we build against libmysqlclient16, it will not install unless that lib is installed, so nothing needs to be done from our part. Again, we're already making sure the correct client version is used as part of bug #52682.

Therefore there's no new action required for this report.