On 12/15/05, Clemens Fruhwirth <[EMAIL PROTECTED]> wrote: > What about using wxCL as McCLIM backend?
I am scared by certain issues with wxCL. Currently, it only works on CLisp. While this isn't normally a stubling block, it seems that large portions of the wxCL code use the CLisp FFI package. This means wxCL is held to the GPL, and cannot be licensed as LGPL. [1] Basing McCLIM on wxCL would then make McCLIM GPL, creating a big licensing mess for the communities working on McCLIM currently. I suspect that wxCL can get away with relicensing GPL code simply because it hasn't appeared as a threat on anyone's radar. Googling for the mailing list thread in which CLisp was initially forced to become GPL would also explain the CLisp authors' reluctance to step in and correct the authors of wxCL. A GPL fork of McCLIM would work. I love the GPL as a license and tool for free software, but if one of the goals of the Gardeners is to make a distribution of Common Lisp that both businesses and individuals feel is "theirs", then I think the LLGPL would be a good place to draw the line. 1] http://www.findinglisp.com/blog/2005/12/reddit-and-lisp-psychosis.html Search for "forces your code to be GPL". This is also implied by most of the COPYRIGHT file in the CLisp distribution. The paragraph on "foreign non-lisp" code also doesn't bode well for licensing issues and wxCL. _______________________________________________ Gardeners mailing list [email protected] http://www.lispniks.com/mailman/listinfo/gardeners
