"Alex Queiroz" asandroq@gmail.com writes:
On Sat, Oct 25, 2008 at 4:58 AM, Christian Jaeger christian@pflanze.mine.nu wrote:
Suppose someone wants to publish his own code based on Gambit (L)GPL so that changes to his/her code will have to be republished. Assume Gambit itself is only BSD licensed; the combination will contain parts under both licenses. Assume to make his own code work, he also had to change Gambit in a number of places; would those changes be LGPL or BSD licensed? (You can't choose LGPL for the whole Gambit files anymore, because the original Gambit code is only licensed under BSD.) Maybe you could switch license within the file, i.e. add another license header in the midst of the file stating (L)GPL before the new function, but at some point this will get impractical, which is why usually such contributions are just made under the same license as the existing file, right? The only practical solution might be to offer the changes only as a patch file, and put the patch under the (L)GPL, but that plays poorly with VCS systems etc.
If Gambit were BSD or MIT licensed, I could change just aprocedure and relicense the whole thing GPL.
No, you can't. You have to own the copyright for that.