From: Steve L. <st...@di...> - 2024-11-18 23:46:09
|
That matches my understanding - any MPL code (including subsequent changes to the original code) has to remain under MPL but it doesn’t infect the MIT/BSD licensed code. That being the case, no objections from me, as long as we document this somewhere. -- Steve On 19 Nov 2024 at 6:33 AM +0800, Jan Nijtmans <jan...@gm...>, wrote: > Hi all, > > Inside Tcl, some files have a different license. For example, > libtommath uses the libtommath licence, compat/dlfcn.h > also has a slightly different license. Inside wish, > x11/*.h also has a slightly different license. > > In order to fix bug [a8e4f76ce4] "load library (dll) from > zipfs-library causes a leak in temporary folder" I > found a useful library, which is under the MPL license, > which is - also - very similar to the BSD license. > > Question: can we approve the MPL license to be > used in separate source-files within Tcl? The exact > text can be found here: > <https://www.mozilla.org/en-US/MPL/2.0/> > > 3.3. Distribution of a Larger Work > You may create and distribute a Larger Work under terms > of Your choice, provided that You also comply with the > requirements of this License for the Covered Software ... > > My conclusion is that - as long as the files MemoryModule.h > and MemoryModule.c are kept under the MPL and fulfill > the restrictions of this license (which they do), this doesn't > impose any restrictions on the rest of the software. > > Regards, > Jan Nijtmans > _______________________________________________ > Tcl-Core mailing list > Tcl...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-core |