Re: libmysqlclient12 and libmysqlclient14
Maurits van Rees wrote:
<snip>
So if I would remove libmysqlclient12 then these packages would be
removed as well. Not all packages that you mention are in this list.
But there are packages that also depend on packages in this list, so
they would be removed too. So let's look one step further:
$ apt-cache rdepends libmysqlclient12 | sed "s/|//" | grep -v "Reverse Depends" | COLUMNS=120 xargs dpkg -l | grep ^ii | sort | uniq | cut -d " " -f3 | xargs -n 1 apt-cache rdepends | sed "s/|//" | grep -v "Reverse Depends" | COLUMNS=120 xargs dpkg -l | grep ^ii | sort | uniq
ii libdbd-mysql-perl 2.9006-1 A Perl5 database interface to the MySQL database
ii libmyodbc 3.51.09-1 the MySQL ODBC driver
ii libmysqlclient12 4.0.24-10sarge1 mysql database client library
ii mysql-client-4.1 4.1.11a-4sarge2 mysql database client binaries
ii php4-mysql 4.3.10-16 MySQL module for php4
ii phpmyadmin 2.6.2-3 set of PHP-scripts to administrate MySQL over the WWW
ii python-mysqldb 1.2.1c2-1 A Python interface to MySQL
ii python2.2-mysqldb 1.2.1c2-1 A Python interface to MySQL
ii python2.3-mysqldb 1.2.1c2-1 A Python interface to MySQL
ii unixodbc 2.2.4-11 ODBC tools libraries
For mysql-client-4.1 to require libmysqlclient12 is so wrong I can't even
contemplate it rationally. It should require libmysqlclient14 only, as the
upstream intended.
This list already contains the package mysql-client-4.1 that is in
your list, as it depends on libdbd-mysql-perl. (See 'apt-cache
depends mysql-client-4.1'.)
Well, this is one way to start investigating why some packages are
begin removed. Or you could just accept that apt-get knows what it is
doing and is correct in wanting to remove those programs. :)
I assume you're being facetious. I'd worry if you were serious.
BTW, if I
try aptitude it wants to remove roughly the same packages that you
mention. So switching package managers would do you no good.
I don't want to switch package managers. I want to do the right thing,
which is to have all my database connections to the MySQL *4.1* server
on my box going through libmysqlclient14, as the upstream intended.
Anything else is useless to me, as I can't downgrade to MySQL 4.0, I'm
using MySQL 4.1 specific code in hundreds of places.
Is there a workaround using Debian package management?
--
Christopher L. Everett
Chief Technology Officer www.medbanner.com
MedBanner, Inc. www.physemp.com
Reply to: