; to ask the opinion of more people.
>
debian-legal@lists.debian.org
--
Best Regards
LI Daobing
--
To UNSUBSCRIBE, email to debian-legal-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t; exception even if they don't directly use the OpenSSL library.
> This could be a problem, eventually.
>
yes, it is really needed, if you want to run OpenSSL and GPL code in
the same process.
--
Best Regards
LI Daobing
--
To UNSUBSCRIBE, email to debian-legal-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sat, Apr 4, 2009 at 17:43, Cristian Greco wrote:
> On Sat, Apr 04, 2009 at 12:00:56PM +0800, LI Daobing wrote:
>
>> On Sat, Apr 4, 2009 at 05:06, Cristian Greco
>> wrote:
>> > [ CCing debian-legal for comments ]
>> >
>> > On Fri, Apr 03, 2009 at 1
ecutable linking is caused by libtorrent-rasterbar (BSD
> code linked against libssl) or some other required libraries/headers. In the
> former case, if linking is caused by the torrent library, all of its clients
> should add such exception.
>
> My thought is that qbittorrent shouldn't be affected by this problem because
> it
> doesn't really link against libssl. And BTW, the source code includes licenses
> such as LGPL, BSD and MIT, so it shouldn't need the exception anyway.
>
I think it need an exception.
GPL licensed code and OpenSSL licensed code should not run in the same process.
--
Best Regards
LI Daobing
--
To UNSUBSCRIBE, email to debian-legal-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
. Would this still be allowed if the documentation is
> generated from LGPL source files?
>
I think you can regenerate it again, so it can be under LGPL license
--
Best Regards,
LI Daobing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
em fulfill the license (GPL with openssl
exception), am I corret?
Thanks.
--
Best Regards,
LI Daobing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
clearly marked as such, and if the derived work is
* incompatible with the protocol description in the RFC file, it must be
* called by a name other than "ssh" or "Secure Shell".
*/
--
Best Regards,
LI Daobing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
7 matches
Mail list logo