Ar an séú lá déag de mí Lúnasa, scríobh SL Baur: And by file-name-handler-alist , invisibly to the user. See 87zm1byrtr.fsf(a)gmx.de in the xemacs-review archives. The relevant paragraphs from the FSF copyright people: We believe that if someone shipped a GPLv3 Tramp with XEmacs, the entire XEmacs package would need to be shipped under the terms of GPLv3 as well. If developers wanted to leave GPLv2-or-later notices on the pieces under that license, to show other users which code had which license, that would be fine, but anybody distributing the whole combination would have to follow the rules of GPLv3. While I appreciate that Tramp is separable from the rest of XEmacs, they're not exactly completely independent works, either. As I understand it, if you take an XEmacs package that has Tramp bundled inside that, and then build and install that the normal way, XEmacs will automatically load Tramp on startup. To a user who wasn't familiar with the XEmacs architecture, there would be no reason to believe that the remote editing features were somehow separate from the rest of the editor. So, an XEmacs+Tramp distribution is not mere aggregation, but instead a combination, and you need to follow the terms of both programs' licenses to make that combination. In this case, the way to do that is to follow the terms of GPLv3, since that's what Tramp offers, and it's an option that's available for the rest of XEmacs too. Now of course that hasn’t been tested in court, but it’s not prima facie an unreasonable interpretation. -- On the quay of the little Black Sea port, where the rescued pair came once more into contact with civilization, Dobrinton was bitten by a dog which was assumed to be mad, though it may only have been indiscriminating. (Saki) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta