Garth Sheldon-Coulson <g...@mit.edu> writes: Hi Garth,
> Another option Rich could consider for Clojure is the Mozilla > tri-license (GPL/LGPL/MPL). > > http://www-archive.mozilla.org/MPL/relicensing-faq.html > > The tri-license would remove any lingering ambiguity about building > GPLed Clojure projects. What's the point of licensing something under GPL and LGPL? AFAIK, you can always take a LGPL project and relicense it as GPL. > But actually I believe the status quo is already quite permissive. > The fact that Clojure is EPLed doesn't mean you can't write GPLed apps > using it.* The EPL-GPL incompatibility bites you only when you try to > GPL something that is a "derivative work" of Clojure. Exactly, but everything that goes beyond communication over pipes / fifos / command line invocation is derivative work according to the FSF. So compiling the clojure sources we've written with the EPL clojure compiler is ok, but since our code calls functions in clojure.core and clojure.contrib it is derivative work, and thus the GPL incompatibility bites us. Well, but we can use the GPL with some special "we allow the usage of clojure" exception. That's a bit of inconvenience, but at least we don't have to exclude clojure only because of licensing issues. Bye, Tassilo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
