On Mon, Dec 8, 2008 at 4:35 PM, Michael Goffioul <[EMAIL PROTECTED]> wrote: > On Mon, Dec 8, 2008 at 2:42 PM, Jaroslav Hajek <[EMAIL PROTECTED]> wrote: >> The package must be GPLed, no question. The original library, >> certainly not. Or I must be missing something important. If my >> software A links to a library B and to Octave, the A is a derivative >> work of both B and of Octave, but certainly that does not make B a >> derivative work of Octave! If the license of B does not prohibit >> GPL-licensed derivative works, everything is OK. > > I'm not an expert in licensing, but I know that jwe's interpretation > is that the library B must be distributed under a GPL-compatible > license, which MOSEK is not. > >> I think the situation is no different from, say, MinGW linking to Windows >> API. > > These are part of the OS. GPL makes an exception for components > that are part of the system. > > Michael. >
Huh, sorry. I've found the relevant section and it appears you're right. Blimey, and I always thought GPL allows this kind of linking. Thanks for the education :) regards -- RNDr. Jaroslav Hajek computing expert Aeronautical Research and Test Institute (VZLU) Prague, Czech Republic url: www.highegg.matfyz.cz ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
