* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-07-23 09:02]:
> Quoting Rafael Laboissiere <[EMAIL PROTECTED]>:
>> Otherwise, could you please point me to where the "automatic promotion" you
>> mention above is documented?
>
> I had a quick look online, but couldn't really find any explaination
> that fits well into this situation. What I said is just my
> understanding, and I am really no expert. Section 3 of the LGPL mentions
> something that's fairly close to this situation, but I'm not sure if it
> fits perfectly. Perhaps you should simply ask Debian Legal or the FSF. At
> least they know what they're talking about :-)
I will eventually do it but I found a FAQ that could fit in [1]:
If I add a module to a GPL-covered program, do I have to use the GPL as
the license for my module?
The GPL says that the whole combined program has to be released under
the GPL. So your module has to be available for use under the GPL.
For me, that says that ANN *_must_* be released under the GPL. However, the
second paragraph of that FAQ adds to the confusion:
But you can give additional permission for the use of your code. You
can, if you wish, release your program under a license which is more lax
than the GPL but compatible with the GPL. The license list page gives a
partial list of GPL-compatible licenses.
[1] http://www.gnu.org/licenses/gpl-faq.html#GPLModuleLicense
--
Rafael
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
