psolaiyappan at novell.com
Fri Dec 2 10:28:46 MST 2011
Thanks for letting us know.
We discussed about this issue further and now Novell OES file access protocol implementations dynamically links the libsmbsharemodes package.
>>> Jeremy Allison <jra at samba.org> 12/1/2011 12:01 AM >>>
On Wed, Nov 30, 2011 at 12:27:58PM +0100, David Disseldorp wrote:
> On Tue, 29 Nov 2011 11:07:54 -0800
> Jeremy Allison <jra at samba.org> wrote:
> > On Tue, Nov 29, 2011 at 03:27:59PM +0100, Volker Lendecke wrote:
> > > Right. But the problem is that the Samba Team has given the
> > > promise to keep this library up to date forever, an
> > > important OEM is using it in a proprietary product. So we
> > > are pretty stuck here unfortunately.
> > Why don't we wait to hear from the important OEM..
> I raised this issue with the OES team, Solai (cc'ed) provided the
> response shown below...
> Cheers, David
> On Tue, 29 Nov 2011 23:47:47 -0700
> "Solaiyappan Perichiappan" <psolaiyappan at novell.com> wrote:
> > Hi,
> > Novell File access protocols implementation like NCP, CIFS and AFP uses libsmbshaemodes.so to place share mode locks in the locking.tdb for cross protocol lockings.
> > Currently we are statically linking to the libsmbsharemodes.so library provided by novell-oes-samba-libsmbsharemodes0 package.
You do realize that staticly linking to this means you
have to provide .o files for the binary you ship so
that users can re-link, right ?
Otherwise you're violating the LGPL license for this
Just making sure that team knows :-).
More information about the samba-technical