Re: A plea for dynamically loadable extension modules

[Thien-Thi Nguyen <ttn@gnuvola.org>]

() 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