From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: dhruva <dhruvakm@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: A plea for dynamically loadable extension modules
Date: Sun, 19 Aug 2007 14:51:40 +0200 [thread overview]
Message-ID: <87zm0nvg9v.fsf@ambire.localdomain> (raw)
In-Reply-To: <e3f230850708182022l45d3b24p4627523ddaeddc1@mail.gmail.com> (dhruva's message of "Sun\, 19 Aug 2007 08\:52\:29 +0530")
() dhruva <dhruvakm@gmail.com>
() Sun, 19 Aug 2007 08:52:29 +0530
Would this be a feasible approach?
i don't think so. the intent is that the action of linking GPL code to
non-free code should not be prohibited. instead, doing so should extend
GPL protections to the non-free code, in essence "freeing" it. i use
quotes because to realize the new state of the module's ("formerly"
non-free) code requires downstream action of (imputes responsibility to)
someone, possibly not the same person as the user.
here is my take on what this means, concretely:
A/ user does not redistribute anything.
=> module's status is irrelevant
(GPL only pertains to *re*distribution)
B/ user redistributes w/in organization.
=> module's status is irrelevant
(GPL only pertains when organization boundary is crossed)
C/ user redistributes outside organization.
=> GPL requires that to redistribute Emacs + module, source code for
both Emacs and the module be also available; if source for the module
cannot or will not be available, GPL prohibits such redistribution
altogether.
to sum up, link time exception based on `(GPL-p module)' does not
address the intent (assuming i understand both the intent and your
proposal).
thi
next prev parent reply other threads:[~2007-08-19 12:51 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
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 [this message]
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=87zm0nvg9v.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=dhruvakm@gmail.com \
--cc=emacs-devel@gnu.org \
/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.