From: Gergely K. <ger...@ma...> - 2010-03-26 20:56:25
|
Hi, 2010/3/25 Arno Puder <ar...@pu...> > > > Just to clarify: This means that if no part of the compatibility library > > (and of course the Android library) of XMLVM is used in a project, then > > the resulting software is not subject to the GPL, and it can be > > redistributed under any license without a linking exception. > > > > Is this the correct interpretation? > > Yes. If you only used XMLVM's compiler, the generated code would not be > covered by the GPL. Note however, that the generated code without the > library (e.g., xmlvm.m) will not do much. Once you link xmlvm.m, the GPL > does apply to your application. > So essentially if one replaces everything in compat-lib with a new implementation, then it is fine. > > Any contribution that we (or anybody else) make will have 2 parts: > > - original work: something that was created independently of the > > existing parts of XMLVM, e.g. a new class or method in a class. > > - derived work: something that was created based on existing code in > > XMLVM, e.g. when a method is changed to fix a bug, or the xsl is > > changed...etc. > > It is my interpretation of the GPL that these two cases would both be > considered derived work. How you break up your contribution is up to > I am confused. I develop code that is not based on XMLVM in any way, like the NSRecursiveCondition in the patch I submitted. Why would you consider it derived work? So I can't reuse it in a different project without making it GPL? Or am I misunderstanding something? Best Regards, Gergely -- Kis Gergely MattaKis Consulting Email: ger...@ma... Web: http://www.mattakis.com Phone: +36 70 408 1723 Fax: +36 27 998 622 |