On Tuesday 04 November 2008 17:21, r wrote: > ... > > OTOH, what is this incompatibility really about? If I include a GPL > library and publish my code under CPL, the source code is still > there, isn't it?
It's about how much control you retain over your own work once you publish it. GPL has strong contagion clauses, as I understand it. I'm not sure to what degree this is an oversimplification or even whether it's accurate, but keep in mind that "free," as conceptualized by the FSF and "open source" are quite distinct. Thus, mixing licenses oriented towards the FSF philosophy of "software freedom" with the much more limited notion of "open source" is likely to be problematic. > Or, what if I publish my clojure code under a dual license GPL/CPL? > That IMHO should keep everyone happy. Or make everyone upset?? Seriously, I don't know enough about FLOSS licenses individually, let alone what happens when you offer alternatives or combinations. > -r. Randall Schulz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
