Comment 7 for bug 1003776

On Mon, Jun 18, 2012 at 06:44:30PM -0000, Ignacio Nin wrote:
> Fixed in 5.1, ready for next release.
>
> For 5.5, it may be a little more complicated. Unfortunately, official
> libdbd-mysql-perl depends on libmysqlclient16 (note the version
> dependency) instead of libmysqlclient, so having percona-server-
> server-5.5 depend on libdbd-mysql-perl would make it effectively depend
> on libmysqlclient16 (apart from libmysqlclient18, on which it already
> depends).

Debian package for libdbd-mysql-perl on testing depends on libmysqlclient18. You
say for older releases from debian/ubuntu where this percona version is
backported ?

>
> This may be an acceptable solution, but I'm looking into more options.

Yeah, it doesn't sound ideal. But if it's only for older releases (we have a
ubuntu natty server with libmysqlclient16 and libmysqlclient18 with no problems)
and it doesn't cause any problems it seems acceptable to me.

If we need to avoid using different libmysqlclient versions, maybe the
appropiarte thing is to use libmysqlclient16 on those releases for percona too
(if that is possible). But to backport all packages that use libmysqlclient, to
make them use libmysqlclient18 seems kind of messy and a good place for bugs
IMHO. But maybe there are more options besides these two ?

Also, looking at the files both libmysqlclient versions install, it seems they
shouldn't conflict. They install a .so with the version, so tools linked agains
one shouldn't conflict with the other. Also, libmysqlclient18-dev is not
neccesary to install so it shouldn't cause any damage compiling (maybe at link
time if the version is not specified).

Anyways, in our server we have both versions installed and it didn't cause any
troubles (although I understand is not an ideal solution). If you don't have
such an environment, let me know if you want me to test something :)

Thanks a lot,
Rodrigo