Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Sun, Feb 13, 2005 at 12:07:06PM +1100, Paul Hampson wrote: So what if we had two editions of libmysqlclient, one of them ssl-enabled and the other - as currently - not? That would allow using ssl whenever possible. I think that could be done, without breaking things. That's funny. Didn't we spend all that time since Woody merging lib-*-ssl back into lib-*? That was perfecly reasonable at the time of libmysqlclient10, when it was LGPL. Unfortunately the change in the license was not among the possibility considered for the near future... -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Sat, Feb 12, 2005 at 12:39:58AM -0800, Steve Langasek wrote: Nice, so we should check that any linked GPL library directly (obviuolsy) or indirectly (with N=1,2,3... levels of indirection) linked against openssl adds the exception. No, we should simply not be linking libmysqlclient against OpenSSL. The exemption was needed because there exists software that uses both libmysqlclient and libssl, but making libmysqlclient itself use libssl just because we now have the exemption will cause licensing problems for applications which currently do *not* depend on libssl. That's clear, I meant simply that if program A links libB which links libC which links libssl, than both A, libB and libC should add the exception, isn't it? That's independently from having A using libssl functions directly or not. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Sat, Feb 12, 2005 at 09:53:34AM +0100, Francesco Paolo Lovergine wrote: Nice, so we should check that any linked GPL library directly (obviuolsy) or indirectly (with N=1,2,3... levels of indirection) linked against openssl adds the exception. No, we should simply not be linking libmysqlclient against OpenSSL. The exemption was needed because there exists software that uses both libmysqlclient and libssl, but making libmysqlclient itself use libssl just because we now have the exemption will cause licensing problems for applications which currently do *not* depend on libssl. That's clear, I meant simply that if program A links libB which links libC which links libssl, than both A, libB and libC should add the exception, isn't it? That's independently from having A using libssl functions directly or not. That's true; I'm merely pointing out the importance of not turning libmysqlclient into libC here. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Sat, Feb 12, 2005 at 09:17:44AM -0800, Steve Langasek wrote: On Sat, Feb 12, 2005 at 09:53:34AM +0100, Francesco Paolo Lovergine wrote: Nice, so we should check that any linked GPL library directly (obviuolsy) or indirectly (with N=1,2,3... levels of indirection) linked against openssl adds the exception. No, we should simply not be linking libmysqlclient against OpenSSL. The exemption was needed because there exists software that uses both libmysqlclient and libssl, but making libmysqlclient itself use libssl just because we now have the exemption will cause licensing problems for applications which currently do *not* depend on libssl. That's clear, I meant simply that if program A links libB which links libC which links libssl, than both A, libB and libC should add the exception, isn't it? That's independently from having A using libssl functions directly or not. That's true; I'm merely pointing out the importance of not turning libmysqlclient into libC here. So what if we had two editions of libmysqlclient, one of them ssl-enabled and the other - as currently - not? That would allow using ssl whenever possible. I think that could be done, without breaking things. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Fri, Feb 11, 2005 at 03:30:59PM -0800, Steve Langasek wrote: On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote: On 2005-02-11 sean finney wrote: On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote: FYI: new mysql FLOSS includes OpenSSL license, so many packages could migrate to current libmysqlclient starting from no starting from now.. that's great to hear! i'm cc'ing the relevant wishlist bug i have open against mysql-server. christian: any chance of getting an openssl enabled version of the mysql-client and mysql-server packages? Yes, I will re-enable openssl in the next upload. Please make sure this does not introduce an openssl dependency to libmysqlclient itself; just because MySQL AB have granted a license exception for OpenSSL does not mean everyone who links to libmysqlclient has done so. I know of at least one GPL-without-exception package that is now using libmysqlclient12 in Debian. Nice, so we should check that any linked GPL library directly (obviuolsy) or indirectly (with N=1,2,3... levels of indirection) linked against openssl adds the exception. This is a great reason to move asap all possible programs to gnutls, indeed. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Sat, Feb 12, 2005 at 09:14:26AM +0100, Francesco Paolo Lovergine wrote: On Fri, Feb 11, 2005 at 03:30:59PM -0800, Steve Langasek wrote: On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote: On 2005-02-11 sean finney wrote: On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote: FYI: new mysql FLOSS includes OpenSSL license, so many packages could migrate to current libmysqlclient starting from no starting from now.. that's great to hear! i'm cc'ing the relevant wishlist bug i have open against mysql-server. christian: any chance of getting an openssl enabled version of the mysql-client and mysql-server packages? Yes, I will re-enable openssl in the next upload. Please make sure this does not introduce an openssl dependency to libmysqlclient itself; just because MySQL AB have granted a license exception for OpenSSL does not mean everyone who links to libmysqlclient has done so. I know of at least one GPL-without-exception package that is now using libmysqlclient12 in Debian. Nice, so we should check that any linked GPL library directly (obviuolsy) or indirectly (with N=1,2,3... levels of indirection) linked against openssl adds the exception. No, we should simply not be linking libmysqlclient against OpenSSL. The exemption was needed because there exists software that uses both libmysqlclient and libssl, but making libmysqlclient itself use libssl just because we now have the exemption will cause licensing problems for applications which currently do *not* depend on libssl. This is a great reason to move asap all possible programs to gnutls, indeed. There are plenty of reasons to move software to gnutls, but doing so is non-trivial. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Sat, Feb 12, 2005 at 08:25:41PM +0100, Francesco Paolo Lovergine wrote: On Sat, Feb 12, 2005 at 09:17:44AM -0800, Steve Langasek wrote: On Sat, Feb 12, 2005 at 09:53:34AM +0100, Francesco Paolo Lovergine wrote: Nice, so we should check that any linked GPL library directly (obviuolsy) or indirectly (with N=1,2,3... levels of indirection) linked against openssl adds the exception. No, we should simply not be linking libmysqlclient against OpenSSL. The exemption was needed because there exists software that uses both libmysqlclient and libssl, but making libmysqlclient itself use libssl just because we now have the exemption will cause licensing problems for applications which currently do *not* depend on libssl. That's clear, I meant simply that if program A links libB which links libC which links libssl, than both A, libB and libC should add the exception, isn't it? That's independently from having A using libssl functions directly or not. That's true; I'm merely pointing out the importance of not turning libmysqlclient into libC here. So what if we had two editions of libmysqlclient, one of them ssl-enabled and the other - as currently - not? That would allow using ssl whenever possible. I think that could be done, without breaking things. That's funny. Didn't we spend all that time since Woody merging lib-*-ssl back into lib-*? -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
Hello On 2005-02-11 sean finney wrote: On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote: FYI: new mysql FLOSS includes OpenSSL license, so many packages could migrate to current libmysqlclient starting from no starting from now.. that's great to hear! i'm cc'ing the relevant wishlist bug i have open against mysql-server. christian: any chance of getting an openssl enabled version of the mysql-client and mysql-server packages? Yes, I will re-enable openssl in the next upload. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#291945: eleventh-hour transition for mysql-using packages related to apache
On Fri, Feb 11, 2005 at 03:31:44PM +0100, Christian Hammers wrote: On 2005-02-11 sean finney wrote: On Fri, Feb 11, 2005 at 10:15:55AM +0100, Francesco P. Lovergine wrote: FYI: new mysql FLOSS includes OpenSSL license, so many packages could migrate to current libmysqlclient starting from no starting from now.. that's great to hear! i'm cc'ing the relevant wishlist bug i have open against mysql-server. christian: any chance of getting an openssl enabled version of the mysql-client and mysql-server packages? Yes, I will re-enable openssl in the next upload. Please make sure this does not introduce an openssl dependency to libmysqlclient itself; just because MySQL AB have granted a license exception for OpenSSL does not mean everyone who links to libmysqlclient has done so. I know of at least one GPL-without-exception package that is now using libmysqlclient12 in Debian. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
