lkml.org 
[lkml]   [1999]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Announce: DinX windowing system 0.2.0
In <Pine.LNX.4.10.9912260546050.1035-100000@asdf.capslock.lan> Mike A. Harris (mharris@meteng.on.ca) wrote:
MH> On Fri, 24 Dec 1999, Khimenko Victor wrote:

>>>> category: console/graphics
>>>>
>>>> brief: Windowing system, uses Linux framebuffer.
>>>>
>>>> license: MPL with GPL option
>>
>>> That way you are not allowed to link is statically into kernel...
>>
>>Hmm. Why not ? Since GPL option is there you can link it even without usage
>>of "GPL hole".

MH> Because the MPL licence is useless in the context of the
MH> software. The software is code that sits with the kernel. The
MH> only code that may be compiled into the kernel is code that is
MH> GPL'd or under a GPL compatible licence (which MPL is not).
MH> Thus, licencing under MPL makes the code useless, or it voids the
MH> MPL licence. If the only way to use the code is to use the GPL
MH> licence, then GPL wins.

But this code can be compiled as module as well (may be not right now, though).
And then you can use any license at your choice. You need GPL if you want to
link it statically in kernel and you can add proprietary extensions (as MPL
allows) when using it as module. What's wrong here ?

MH> So to simplify things, just say what it really is:

MH> GPL licenced. Then say that others may obtain or use the code
MH> under MPL licence as well. If using the MPL licence however,
MH> they will not be able to link with the Linux kernel.

Link - no. Load as module - yes. So MPL is usable here.





-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.120 / U:2.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site