Jerry James writes:
Are you talking about changing the "GPL v2 or later"
notices? We're
covered under the "later" clause. Also, we *can't* do that unless we
have the permission of all authors. Isn't that right?
We can change the permissions to a subset of the licenses we
received. Eg, we could do something like "GPLv2 or later, provided
that the major version is *even* and the minor version is 1 or
greater." (Speaking of silly....) In particular, we can stop
distributing under GPLv2 (and must if we wish to sync FSF code, since
they no longer grant GPLv2 licenses, and so those won't be in the set
of licenses we receive from them).
The point is that "GPL, v2 or later" is not a single license, it is a
*set* of licenses, each of which individually gives us permission to
redistribute under that license and that license only. Ie, to state
that extensionally, GPLv2 is in "GPL, v2 or later", so we have a GPLv2
license, and we can grant that license to our downstream. GPLv3 is
also in "GPL, v2 or later", so we have and can grant that one, too, or
not, as we please. We can do either or both, but until GPLv4 is
published, we can't distribute unless we choose one of GPLv2 or GPLv3,
since XEmacs contains code licensed to us only under "GPL, v2 or
later". We can't use a license that is not in the intersection of all
copyleft licenses we have received for code in our derivative work.
If that intersection is empty, we can't distribute.
More silliness: we could, in theory, distribute under "GPL, v4 or
later", but since that hasn't been published yet, nobody can do
anything but run XEmacs with it (according to the FSF theory that
running a program is not regulated by copyright).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta