On Mon, Apr 14, 2003 at 04:16:12PM +0200, Christian Hammers scribbled: > On Mon, Apr 14, 2003 at 04:10:11PM +0200, Francesco P. Lovergine wrote: > > > > > So, what *am* I supposed to do? Rebuild against libmysqlclient12 > > > > > and break licenses? Not rebuild and have an uninstallable > > > > > snort-mysql? > > > > > > > > The only viable approaches seem to be (in random order) > > > > > > > > * fork libmysqlclient > > > > * convince the MySQL folks to revert their license change > > > > * switch to postgres > > > > * get upstream developers to add a clause to their license to permit > > > > linking to OpenSSL or move to GnuTLS (only an option if your > > > > application has an GPL compatible license) > > > > > > Can libmysqlclient be built without encryption support (OpenSSL or > > > GnuTLS)? > > libmysqlclient10 and 11 do not support OpenSSL. libmysqlclient12 does > optionally link against OpenSSL. > > OpenSSL will stay in the main mysql packages but I ask the MySQL people How viable would be to add a new package for libmysqlclient12 that wouldn't link against openssl? libmysqlclient-nossl12 or something?
> if they understood which problems the license change implies and if they > want to keep it. In the meantime, the best thing is probably to add an > upstream permission to link against OpenSSL. Seems to me that it might be easier to just create that other non-ssl version of libmysqlclient... marek
pgpeKSEiainJx.pgp
Description: PGP signature
