Package: libmysqlclient16 Version: 5.1.22rc-1 Severity: wishlist Dear mysql maintainers,
there will be mysql support in libaprutil, which will use libmysqlclient_r.so. Together with php's mysql extension, this means that both libmysqlclient_r.so and libmysqlclient.so will be loaded into Apache. This is probably a very bad idea, since both libraries use the same symbols and symbol versions. A conversation on #debian-devel with seanius, vorlon, and peterS came to the conclusion that the best solution would be to have libmysqlclient_r and libmysqlclient use different symbol versions. To have only one mysql library transition until lenny release, this would need to be implemented in the first upload of 5.1 to unstable. Other suggested solutions were - link php-mysql to libmysqlclient_r - make libmysqlclient symlink to libmysqlclient_r but these might cause unnecessary performance degradation. (Although I don't know whether this is really an issue). Any thoughts? Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
