On Thursday 18 August 2005 9:51 am, John H. Robinson, IV wrote: > Not true. OpenSSL is *very* hurt by this as their code cannot be used in > any GPL application, without a special licensing. GNUtls does not suffer > from this, but it is not as featureful as OpenSSL yet.
OpenSSL, I believe, is under the BSD license, right? Perhaps I'm not understanding the interactions of licenses, here, but what prevents one from using OpenSSL in an application that requires SSL support (by, say, linking to the OpenSSL libraries), if your goal is to add such SSL support to a GPL application? > > I personally tend toward BSD licenses because GPL licenses kinda suck > > when abandoned code is involved. > > Howso? I can see problems where you want to *change* the license, or if > you want to appropriate the code in your own, prorietary (read: non open > and free) project. > > Short of those two situations, what problems have you experienced? Project, originally released under GPL, is completely abandoned. Your project, to be released BSD, requires functionality provided by abandoned project. What do you do? I'm of the firm belief that all licenses suck, to varying degrees of vacuum. Gregory -- Gregory K. Ruiz-Ade <[EMAIL PROTECTED]> OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
