From: Richard Stallman <rms@gnu.org>
Cc: mlang@delysid.org, nferrier@tapsellferrier.co.uk, emacs-devel@gnu.org
Subject: Re: A plea for dynamically loadable extension modules
Date: Thu, 31 Jul 2003 22:20:24 -0400 [thread overview]
Message-ID: <E19iPWq-00042N-F9@fencepost.gnu.org> (raw)
In-Reply-To: <200307301313.WAA06615@etlken.m17n.org> (message from Kenichi Handa on Wed, 30 Jul 2003 22:13:49 +0900 (JST))
So, as far as Emacs is linked with X (by regarding X library
as something fundamental one as libc), it's impossible to
guarantee the above condition.
I think that dynamic linking of these plug-ins that are meant
for use with X does not entail any violation of the GPL,
because these plug-ins do not relate specifically to Emacs
in any way.
If the plug-in relates specifically to Emacs, then our position
is that it constitutes an Emacs extension and has to be covered
by the GPL. However, it would be nice not to have to go to court
about that, and if we don't have dynamic linking then we won't
have to.
next prev parent reply other threads:[~2003-08-01 2:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 12:16 A plea for dynamically loadable extension modules Mario Lang
2003-07-30 12:42 ` Nic
2003-07-30 13:13 ` Kenichi Handa
2003-08-01 2:20 ` Richard Stallman [this message]
2003-07-30 13:43 ` Mario Lang
2003-07-30 14:24 ` Jason Rumney
2003-07-30 14:40 ` Mario Lang
2003-07-30 15:25 ` Paul Jarc
2003-08-01 2:20 ` Richard Stallman
2003-08-01 15:44 ` Paul Jarc
2003-08-04 0:08 ` Richard Stallman
2003-07-30 19:02 ` Kevin Rodgers
2007-08-17 21:30 ` Leo
2007-08-19 0:45 ` Richard Stallman
2007-08-19 1:33 ` Leo
2007-08-19 3:22 ` dhruva
2007-08-19 7:59 ` Stephen J. Turnbull
2007-08-19 12:51 ` Thien-Thi Nguyen
2007-08-19 13:06 ` David Hansen
2007-08-19 22:30 ` Richard Stallman
2007-08-19 22:31 ` Richard Stallman
2003-07-31 4:10 ` Stephen J. Turnbull
2003-07-31 7:56 ` David Kastrup
2003-07-31 9:59 ` Stephen J. Turnbull
2003-07-31 18:57 ` Alex Schroeder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E19iPWq-00042N-F9@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mlang@delysid.org \
--cc=nferrier@tapsellferrier.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.