Elastic promises "open"—delivers proprietary
Elastic promises "open"—delivers proprietary
Posted Jan 28, 2021 16:59 UTC (Thu) by kemitchell (subscriber, #124442)In reply to: Elastic promises "open"—delivers proprietary by Wol
Parent article: Elastic promises "open"—delivers proprietary
<blockquote><p>You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.</p></blockquote>
Posted Jan 28, 2021 20:24 UTC (Thu)
by Wol (subscriber, #4433)
[Link]
If part of the "Entire Work" is derivative of GPL, then, as a *single derivative item*, it can be licenced under the GPL.
But if the "Corresponding Source" contains large chunks of my MIT-licenced work, you can NOT licence the corresponding source as GPL because I didn't give you permission to relicence my work. What you CAN do is distribute the entire corresponding source AS IF it was GPL.
Note that the terms "Entire Work" and "Corresponding Source" imply that the two are completely separate items (linked by the fact that if you pass the "corresponding source" through a compiler/linker, you get the "entire work" as said separate item).
Cheers,
Elastic promises "open"—delivers proprietary
Wol