--- On Mon, 8/16/10, Ralph Giles <[email protected]> wrote:
> From: Ralph Giles <[email protected]> > Subject: Re: [Bf-committers] libreDWG > To: "bf-blender developers" <[email protected]> > Received: Monday, August 16, 2010, 12:42 PM > On 16 August 2010 09:16, Ton > Roosendaal <[email protected]> > wrote: > > > Our license is "compatible" because of the ".. and > later", but if you > > combine it the code probably becomes v3 exclusively, > in its entirety. > > Yep. Although the GPLv2 sections still make a difference in > that one > can distribute builds omitting the GPLv3 code as GPLv2, or > reuse that > code in other GPLv2 projects. > > There's already some "GPLv3 or later" code in the blender > tree, by the > way. Notably the audaspace module is LGPLv3 and some of the > python > scripts are GPLv3, so it looks like the overall license for > 2.5 has > already become GPLv3. For audaspace it doesn't matter (LGPLv3 doesn't force anything on the rest of the code). For the scripts, it depends what scripts (in what direction the dependencies work). GPLv3 code can depend (link with) GPLv2 code without making the later GPLv3. Martin _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
