On Fri, Jan 27, 2006 at 03:42:29PM +0100, Simon Oosthoek wrote:
> hmm, so if I want to contribute to the kernel, but prefer my code to be
> licensed under GPLv3 or higher, I would be unable to submit it to the
> kernel unless I "lower my standards" to GPLv2 or higher?
>
> If someone wants to use that code elsewhere, he can take it from the
> kernel and re-use it in a GPLv2 project and further, which may violate
> the terms of GPLv3 and would therefore conflict with my interests.
>
> Of course, this may be purely theoretical, but it could block people
> from submitting code to the kernel in order avoid the v2 GPL license.
>
> From this, I think it could be concluded that it might turn out to be
> quite harmful if code under GPLv3+ cannot be combined with the linux
> kernel...
That's GPL working *as* *intended*. No, you can't create a derivative
of GPLv2 program and prohibit the use of your modifications in other
GPLv2 programs. It's not just "Linus won't accept it upstream"; it's
"you can't even distribute such fork yourself". And it's 100% intentional -
that's what GPL is about.
As for the harm... We somehow survived years of similar "harmful" situation.
No, you can't put proprietary code in kernel and prohibit other GPLv2
projects to reuse it. Yes, it would theoretically turn some authors of
extremely valuable (but never materializing) code away. And yes, there had
been very similar whining and dire warnings. Nothing new here...
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
