samba license change

[Simo Sorce]

On Wed, 2007-10-10 at 16:54 +0000, Kevin Kofler wrote:

> Looking into it:
> * yes, kio_smb is a separate process,
> * all the code in kio_smb itself is GPLv2+ or LGPLv2+ (There was apparently 
> some improper LGPL->GPL conversion done there though, because there's no such 
> version as the "GPL 2.1" which is referred to. :-/)
> * the kdelibs code which is of course linked in should all be LGPL, thus no 
> problem,
> so yes, Qt is the one problem here, we can start linking kio_smb to GPLv3 or 
> LGPLv3 libraries if and only if and when Trolltech allows the GPLv3 for Qt.

It seem the same sort of situation as for gnome-vfs, it is interesting
to understand how kio_smb communicate and share data with upper layers,
under stricter GPL interpretations what matters is intimate data
structure sharing to define "linking" and therefore derivation, but
IANAL, I guess we need some legal advice on this matter, maybe the
various projects can all agree and ask SFLC to study the situation and
come out with recommendations?

> As for exceptions, you'd also have to consider the GPLv2+ code in kio_smb, 
> which so happens to be "Copyright (c) 2000  Caldera Systems, Inc.", good luck 
> getting these folks to agree to any sort of exception. And without exceptions, 
> I guess the GPLv2+ has to be interpreted as "pick any one version of the GPL", 
> not a mix of both.

GPLv2+ or GPLv3+ or ... means that you are forward compatible, ie, the
work as a whole is redistributed under the uppermost license number.
Individual components keep the license they want when they are on their
own.

Simo.