On Sat, Apr 4, 2009 at 22:25, Cristian Greco <[email protected]> wrote: >> On Sat, Apr 4, 2009 at 17:43, Cristian Greco <[email protected]> >> wrote: >> > 1) What to do in this case? Should all clients based on >> > libtorrent-rasterbar >> > and licensed under the GPL add an exception even if they don't directly >> > use the >> > OpenSSL library? >> > >> libtorrent-rasterbar should provide two packages, one is >> libtorrent-rasterbar-openssl (with openssl enabled), another is >> libtorrent-rasterbar (with openssl disabled), just like libcurl3 and >> libcurl3-gnutls. > > This is not what I was looking for (and this solution wouldn't be useful, as > all existing clients actually require encryption to be enabled). My question > is > if it is really needed for all clients licensed under the GPL to add an > 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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
