Mats Lidell writes:
Well I just thought there would be some problem with merging in
GPLv3
or later code in xemacs-base and still distribute 21.4 that really
needs it to be useful
Since xemacs-base is distributed separately, it's up to the users to
download it and use it with 21.4. Nobody has a leg to stand on
complaining about that, as long as we don't fix bugs occasioned by
incompatibility of 21.4 with GPLv3 code. The problem if we don't
distribute a GPLv3 core is that the FSF can argue that the packages
are not a separate product, but rather part of a larger "real" XEmacs
product that actually is core + packages, and we're just distributing
them separately to avoid complying with the GPLv3 on the packages.
We might need to change the name of future sumos so that the name is
different from that documented in 21.4 INSTALL and perhaps any
packages that GPLv3 code in them. It would be something algorithmic
like appending "-to-avoid-fsf-lawuits" (Hi David! but more likely
"-gplv3") to package and/or sumo names, and 21.5 (but not 21.4) would
know to try those names first.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta