Hi,
>> This would do it - although if this library is a key part of your >> code, licensing your code under the MPL as well as the GPL would be >> fairly pointless, because if anyone wanted to use it under the MPL >> they couldn't link with that library. I didn't understand that... Read on, for the reason I need MPL/GPL... > There are versions of Kylix that don't require GPL, and other c++ > compilers that other developers of his code might use. If you like the > MPL and are only considering this to accomodate folks using the free > version of Kylix then dual licensing is a good option. The problem I was facing when I decided on the license, was that my code uses 2 MPL libraries. So I couldn't take GPL, although I prefered it... But now this problem with Kylix... :) If I license my code in MPL/GPL, can I use both MPL libraries and GPL libraries in the same larger-application ? > Be forwarned that the dual licensing scheme promoted in the boilerplate > allows people to create a GPL-only fork of your code. I've been told > that clause in the boilerplate merely makes explicit what is inherent in > the ability to distribute under the GPL, so modifying the boilerplate > may not help if that is a worry. Isn't really a probelm to me... Thanks guys for the fast reply ! -Carmi
