🚀 go-pugleaf

In article <BURLEY.92Feb4222629@geech.gnu.ai.mit.edu> burley@geech.gnu.ai.mit.edu (Craig Burley) writes:

>For example, if you wanted to sell a proprietary page-layout system that
>integrated with GNU EMACS, you could license/sell the code as source or
>objects with the notice that it only worked when the licensee obtained and
>built GNU EMACS, linking in your changed modules.  As long as what you
>distribute has no GPL-protected code in it, and as long as the licensee
>does not redistribute the rebuilt GNU EMACS (but just uses it internally),
>I can't think of any stipulation in the GPL offhand that prevents you from
>doing that.

I'm not sure about this--it might be that code that has to be linked
into gnumacs has to be GPLed (otherwise, people would wind up with a
partially-unmodifiable Emacs, and your sections could turn into scar
tissue)--but I bet you could provide the functionality in a daemon or
other external program that your GPLed code in Emacs would communicate
with; this is essentially how Emacs gets access to files--just that
the "external program" in this case is the system itself.  Surely the
FSF can't claim that running gnumacs on Unix makes Unix GNUware.  :-)

--
/===========================================================================\
|John (Francis) Stracke         |My opinions are my own.                    |
|Natl. Science Center Foundation|===========================================|
|Augusta, GA                    |What do you mean, *you're*                 |
|francis@dogwood.atl.ga.us      |  a solipsist?                             |
\===========================================================================/
(Formerly francis@zaphod.uchicago.edu)
-- 
/===========================================================================\
|John (Francis) Stracke         |My opinions are my own.                    |
|Natl. Science Center Foundation|===========================================|
|Augusta, GA                    |What do you mean, *you're*                 |