[fpc-pascal] MPL, LGPL rehashed again

[Jonas Maebe]

On 13 Jun 2008, at 09:41, Graeme Geldenhuys wrote:

> #1
> FBLib uses the standard LGPL. We link that software directly into our
> executables. We don't use it as an external (dynamically linked)
> .so/.dll library.  FBLib is pretty much a wrapper for the Firebird
> libfbclient.so library.  If this poses an issue, it should be fairly
> easy for us to switch to a different library like sqldb included with
> FPC.

If it's plain LGPL and you link it statically, then you have to supply  
all object files of the rest of your program to your customers (when  
they ask for it; and you have to inform them of this right they have,  
by including a copy of the LGPL with your software and referring to it  
in your licence agreement), so they can relink your application with a  
newer version of that library should they wish to do so.

> #2
> I know MPL is not GPL compatible, but we are not creating GPL'ed
> software. We are creating software used in-house for our franchisees.
> We do not sell our software either. So would this be a concern for us?

The GPL and (L)GPL only talk about distributing software. Whether you  
sell it, give it away for free, rent it out or ask for a postcard in  
exchange is irrelevant.

> I'm part of the core developers for tiOPF and am pretty sure that if
> we need to change tiOPF's license to a Modified LGPL or dual license
> it, it should be possible. Again, we link tiOPF directly into our
> executable. Does this pose any issues for us?

MPL is not (modified) LGPL compatible either, so you need a dual  
license.


Jonas