tir, 22 07 2008 kl. 16:48 +0200, skrev Rafael Laboissiere: > This makes the product ann.oct be released under the LGPL and when it is > "linked" at run time against Octave itself, which is GPL'ed, we run into a > license incompatibility problem, apparently. > > Again, I am not a license expert and would love if someone prove I am wrong.
I am also no expert, but the way I understand things is: *) ann.oct is LGPL v2 or later *) Octave is GPL v3 or later right? When you link LGPL and GPL code, then LGPL stuff is "promoted" automatically into GPL. So, the license of ann.oct is automatically changed into GPL v3 or later when it is linked to Octave. So perhaps it's a bit silly to license ann.oct as LGPL v2 or later, but I don't think it's a problem. Søren ------------------------------------------------------------------------- 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
