License for elisp script

License for elisp script

[Vivek Joshi]

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

Hello All,
I am planning to write a elisp script (something similar to gdb mode in
emacs). The script needs to use emacs gui for highlighting and moving
around some custom log files. Do I need to make source code of the script
and related backend scripts/programs (used for log file parsing, etc. )
because of the GNU public license?

Sorry for asking such a stupid question. I tried to look for the answer but
could not.

-- 


With warm regards,
Vivek. J. Joshi.

[-- Attachment #2: Type: text/html, Size: 517 bytes --]

Re: License for elisp script

[Pascal J. Bourguignon]

Vivek Joshi <vivekjjoshi@yahoo.co.uk> writes:


> I am planning to write a elisp script (something similar to
> gdb mode in emacs). The script needs to use emacs gui for highlighting
> and moving around some custom log files. Do I need to make source code
> of the script and related backend scripts/programs (used for log file
> parsing, etc. ) because of the GNU public license?

Make them what?


You can distribute your programs under any license you want (or not
distribute them at all).

You may distribute only the compiled script (.elc), and external
programs.


Of course, if you do so, we won't trust them.



-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: License for elisp script

[Stefan Monnier]

> There are other implementations of emacs lisp than GNU emacs.

Are there such that are not GPL'd and that can run the OP's script?
If so, then he can probably distribute it under a non-GPL license, but
otherwise I think he's bound to the GPL.

> In any case, using a language cannot impose a license.

The issue is not so much the language as the library functions.  All the
Elisp libraries bundled with Emacs are GPL'd, so if he calls any of
those functions he's linking with GPL code and hence needs to use the
GPL as well.


        Stefan