samba license change

Alexander Larsson alexl at redhat.com
Fri Oct 12 07:10:24 UTC 2007


On Wed, 2007-10-10 at 08:41 -0400, Simo Sorce wrote:
> On Wed, 2007-10-10 at 09:15 +0200, Alexander Larsson wrote:
> > On Tue, 2007-10-09 at 20:18 +0300, Ville Skyttä wrote:
> > > On Tuesday 09 October 2007, Simo Sorce wrote:
> > > >
> > > > Ah and btw if someone can check what is the GNOME status wrt this it
> > > > would be nice. Nautilus uses libsmbclient as well.
> > > 
> > > I'm no expert on GNOME stuff but I thought it does so through gnome-vfs.
> > > 
> > > gnome-vfs2.spec has:
> > > License: LGPLv2 and LGPL+ and GPL+
> > > # the daemon and the library are LGPLv2
> > > # the modules are LGPL+ and GPL+
> > > 
> > > libsmbclient is used in modules/smb-method.c, which carries a GPLv2+ notice.  
> > > (Dunno if omission of GPLv2+ qualifies as a bug in gnome-vfs2's License tag.)
> > 
> > Furthermore, the smb module is run in the daemon, so the license of it
> > doesn't affect applications linking to gnome-vfs.
> 
> This is interesting, to be sure we should evaluate though if there is
> intimate communication and sharing of data structures between the daemon
> and the client, but things looks much better in the GNOME camp.

It just uses the standard way to put gnome-vfs modules in the daemon.
Nothing is specific to the smb backend. In fact, any backend can be put
in the daemonb by adding [daemon] to the module config file.




More information about the fedora-devel-list mailing list