[Xen-devel] RE: [RFC PATCH 04/35] Hypervisor interface header files.

["David Schwartz" <davids@xxxxxxxxxxxxx>]

> On 22 Mar 2006, at 08:28, Arjan van de Ven wrote:
>
> >> + * This file may be distributed separately from the Linux kernel, or
> >> + * incorporated into other software packages, subject to the
> >> following license:
> >> + *

> > and what, if any, is the license when distributed with the kernel, as
> > you propose? Right now there doesn't seem to be any at all, and thus it
> > would be undistributable.

> I thought GPLv2 would be implicit. I'll add the short GPL stanza to
> each of the offending source files.

        It seems rather illogical to me to add a GPL stanza. The GPL adds new
rights and imposes requirements on you only if you could get those rights no
other way. Since there is another way, the alternative license, the GPL
requirements would never kick in. Although, as far as I can tell, it doesn't
change or harm anything.

        To be precise, it's like saying "you may use this any way you please, 
or at
your option, you may use it subject to certain restrictions".

        It would make a difference, however, if your notice was excisable, 
allowing
someone to change the license to GPL only. However, your notice is not
excisable, so the license (for this file and any future modifications to it)
will perpetually be less restrictive than the GPL and the GPL requirements
can never kick in.

        The license is clearly GPL-compatible so I see no need to change it.

        The only thing I can think of is that someone is concerned about the
hypothetical case where someone modifies this file, compiles it, distributes
the result, and refuses to distribute the source code to this module under
the reasoning that he opted for the license that had no such requirement.
But that fails the giggle test, since he needs the GPL to distribute the
GPL'd portions of the binary and the GPL requires all source to be
distributed. (If I could do that, I could *certainly* add my own code to the
kernel and refuse to deliver the source to it, since my own code is under
any license I want it to be under. And I can't do that.)

        DS



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel