Mats Lidell writes:
What to do here with the packages and GPLv3 or later code?
My understanding of the law is that packages written to support both
Emacs and XEmacs are separate works, and can't infect XEmacs proper
with GPLv3. However, I don't know what the FSF thinks, and several
3rd party package maintainers refuse to update the XEmacs packages
until we are distributing a GPLv3 core. In many cases this is
unavoidable because they depend on unported features of Emacs 23 or 24.
Do we need two versions of the packages? GPLv2 or later to go with
21.4 and GPLv3 or later to go with 21.5 and later? Or is it only an
issue for xemacs-base?
It's not an issue for any package as far as I can see, once we start
distributing a GPLv3 version of XEmacs. Until then, there's the
question of whether the packages are a separate work from XEmacs core
or not. If they are, then there's no problem. If they aren't, and I
suspect that the party with more lawyers will take that position,
there's a big risk of harassment by the FSF.
Anyway, I've completed translating the ChangeLogs since 21.5.29 into
summaries (modulo a few commits in the last week, none of which will
be hard to add), and probably will finish turning the summaries into
useful text (there's lots of duplication and overlap, and over 600
entries) tomorrow or Monday, so there should be a last GPLv2 release
XEmacs-Beta mailing list