Matthias Benkard on 2008-11-04 08:37:08 -0800: > The CPL doesn't allow me to choose the GPL. Instead, it forces me to > apply a CPL-compatible, GPL-like license -- a thing which may or may > not currently exist, but which will certainly make my library useless > to almost everybody because without GPL compatibility, it in turn > forces a non-GPL-compatible license onto my library's users, who will > probably want to make use of GPL-licensed libraries as well as mine.
I looked into writing an application in Clojure that 1) uses libraries licensed under the GPL with the classpath exception and 2) is licensed under the GPL itself. I concluded that 1 is OK, and that 2 works, as long as you have a classpath exception or something more restrictive along the lines of the OpenSSL exception. That's not exactly what I would want, and I am still uncomfortable with the CPL's choice of law clause (and am unsure how it interacts with GPL+classpath exception software when derived work kicks in), but I think with enough exceptions you can get some messy semblance of what you want. I'd be interested to know if anyone disagrees with the above - working through all of that was a headache. It would be interesting to see the FSF's position on this; I haven't gotten around to emailing them about it. --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
