> > Wouldn't that defeat the entire purpose of the GPLv3? Couldn't > > I take any > > GPLv3 program, combine it with a few lines of Linux code, and > > Tivoize the > > result?
> No. This is not permission to relicense. This is permission to > combine. Each author still gets to enforce the terms of her own code. This makes no sense. We are not talking mere aggregation here, we are talking developmental convergence. If I wrote some code that was in the Linux kernel, how can I enforce the terms of my code (guaranteed write to Tivoize) in the derivative work that it becomes mixed with? > So a tivoizer would have to take out the code licensed under the > GPLv3, and use only the code that permits tivoization. Same as today, > but without the possibility of cooperation for licensees who don't > tivoize. I am baffled how this could possibly work. You understand that the GPLv2 specifically guarantees that any derivative work will be Tivoizable and the people who chose the GPLv2 specifically want it that way? If I chose the GPLv2 over the GPLv3 as a conscious choice, that means I want people to be able to Tivoize any derivative work made from my work that is distributed. DS - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
