> Marco van de Voort napisa?(a): > >>> That is not possible with the GPL, LGPL or even the FPC RTL license. If > >>> you require such credit, people will also not be able to use your > >>> library in a (L)GPL product, because the resulting license will be > >>> incompatible with the (L)GPL.. > >> Understood. But I guess I can live with that :-). Yet, that brings up > >> the idea of double-licencing -- licencing the library as (L)GPL for use > >> with (L)GPL software, and a parallel licence for use in closed source > >> software in which case attribution is needed. I guess that would be > >> possible... > > > > As long as you own all rights to the lib this is possible. However if you > > use parts with different licenses in your lib, this could be troublesome. > > > > (e.g. Jedi-SDL headers or so) > > Actually the Jedi-SDL headers are under the MPL.
This afaik isn't that far off from the FPC version of the LGPL. > As for the problem itself -- the library uses the headers, but doesn't > include them, so I guess the problem is not applicable? Easy to check. Is the implementation empty? Doesn't e.g. wrap and dynload? One could of course always plead the "trivial" defense in such case. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
