Re: git to libgit2 code relicensing

[Miklos Vajna <vmiklos@frugalware.org>]

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

On Sat, Nov 15, 2008 at 05:00:52AM -0800, Junio C Hamano <gitster@pobox.com> wrote:
> Under LGPL, you must provide linkable object files to your (possibly
> closed source) program, so that people who made changes to (or obtained an
> updated version of) a LGPL'ed library can re-link your program and use the
> updated library.  The above does not ask you to do so.
> 
> The way I read LGPL is that "We deeply care about our LGPL library and any
> improvements to it.  Although we do not care at all about how your crappy
> closed source program is written, we want to make sure that the users can
> keep using your program after improvements are made to our library.".  I
> do not think it makes a practical difference when your program uses the
> LGPL library as a shard library from that point of view.

Ah, I see - so this is a "Lesser LGPL". :)

Thank you both Junio and David.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]