* Michael Goffioul <[EMAIL PROTECTED]> [2008-07-21 20:44]: > Isn't it the other way around? You want to release something > under GPLv3 (the ann package in octave-forge), which uses > a library under LGPLv2.1 (the ann library).
According to the GNU Licences Compatibility Matrix, the combination we mention above is okay. However, both src/ann/Copyright.txt and src/ann/binding/ann.i state that the Octave binding is released under the LGPL. This later has in its header: // Copyright (c) 2008, Xavier Delacour <[EMAIL PROTECTED]> // All rights reserved. // // This software and related documentation is part of the Approximate // Nearest Neighbor Library (ANN). This software is provided under // the provisions of the Lesser GNU Public License (LGPL). See the // file ../ReadMe.txt for further information. 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. -- 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
