On Thursday 02 February 2006 01:57, Kyle Moffett wrote:
> But see, even assuming the really odd case of a project consisting of
> one file, the GPL, that project would be completely GPL compatible.
> As the license specifies the licensing terms for the project (IE: the
> GPL), it may not legally be modified _even_ _under_ _copyright_ _law_
> (because it's the project license).
Well ok, but modified copies of it (that aren't the license) could be
made. For the sake of argument, imaging copying the preamble into
another file and adding a few paragraphs there, with a prominent notice of
your modifications. This is allowed by the GPL (the License is the same,
and you're not violating the other terms either as far as I can see). But
it is not allowed by the license for the text of the GPL. Hence the
problem. It's an odd squirrelly corner case of the sort that cause licenses
to bloat up with verbiage.
The out is if the license file is not a portion of the program, in which
case section 2 of the GPL doesn't apply. I think this is what Alan Cox
is arguing. However, while it would be convenient if the License text
wasn't considered part of the program, I'm not sure that reasoning
would hold up in court.
It's also a complete non-issue: both because no-one is going to actually
object to the text of the GPL being there, and because it can be replaced
with a simple link in the extremely unlikely event that the need arises.
Andrew Wade
-
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]
