proposed FAQ entries about licensing

[David Bateman]

Jaroslav Hajek wrote:
> I'm not sure about Windows, but under Linux even MEX compiled files
> contain links to libcruft, liboctave & liboctinterp, which IMHO makes
> them derivatives of Octave. The sources can be distributed under any
> license, if they don't contain Octave-specific stuff.
>
>   
Yes, but theoretically the MEX compiled for Octave can be used with 
Matlab, and thus can be licensed which any license. This is like browser 
plugins, and is what is explicitly written in the FAQ clause propose by 
John. See clause 1 for the conditions of using a MEX...

<quote>

      Code written using Octave's implementation of the Matlab MEX
      interface may be released under the terms of whatever license you
      choose, provided that the following conditions are met:

      1. The plugin should not use any bindings that are specific to
	 Octave.  In other words, the MEX file must use the MEX
	 interface only, and not also call on other Octave internals.
	 It should be possible in principle to use the MEX file with
	 other programs that implement the MEX interface (e.g., Matlab).

      2. The MEX file should not be distributed together with Octave in
	 such a way that they effectively create a single work.  For
	 example, you should not distribute the MEX file and Octave
	 together in a single package such that Octave automatically
	 loads and runs the MEX file when it starts up.  There are other
	 possible ways that you might effectively create a single work;
	 this is just one example.

</quote>

D.

-- 
David Bateman                                dbateman at dbateman.org
35 rue Gambetta                              +33 1 46 04 02 18 (Home)
92100 Boulogne-Billancourt FRANCE            +33 6 72 01 06 33 (Mob)