29 Jul
2009
29 Jul
'09
10:20 a.m.
On Wed, Jul 29, 2009 at 1:08 PM, <laseray(a)gmail.com> wrote:
On Wednesday 29 July 2009 04:21:08 you wrote:
No, that is not true. The GPL requires this to happen, but it does
not cause it to happen. What causes the resulting combined code to be
under the GPL is the fact that it is published under the GPL, not the
fact that it incorporates code that was published under the GPL.
There is nothing particular about the GPL here. It's a license, not a
work of magic. If I provide code to you under some terms and you
incorporate and re-publish the code flouting those terms, then you and
I have a legal problem -- but that's between you and me, it has no
bearing on the conditions under which your users received your
combined work. An appropriate remedy for the problem might be for you
to ensure that you comply with my license (e.g. publish under the GPL)
or desist from publication, but your users can't enact that remedy for
themselves.
Chris
On Wed, Jul 29, 2009 at 3:38 AM,
<laseray(a)gmail.com> wrote:
You are wrong. Read the GPL. Everyone who really knows it understands
that your code comes under the GPL whenever you mix it with other GPL
code. That is the way it works. Whether he wanted to or not, use of GPL code
makes it GPL code.
This is not true. It may simply make it code that was distributed in
violation of the GPL.