[Pkg-samba-maint] nearly built 3.2.0~pre2-1

[Steve Langasek]

On Thu, Mar 27, 2008 at 09:18:36AM +0100, Michael Adam wrote:
> That is right, this (along with subsequent commits) is the cause of the
> libtalloc.so.1 problem. (But spontaneously, I don't know about the symbols
> missing from the vfs modules.)

The missing symbols are a non-issue; dpkg-shlibdeps warns about these
because it has no way of knowing what symbols in a plugin are supposed to
be resolved by the caller, which is the case here.

> When there is no system talloc library (as is there at least in
> SID as Jelmer told me), Samba needs to provide its own. There are
> several choices:

Can you help with fixing the Samba build rules so that it will actually
*use* the system talloc library if present?  I can't see any way to specify
this; the only choices I see are to build against the static in-tree lib,
build against the shared in-tree lib, or link the individual object files
directly without first making a lib, there's no way to tell the build rules
to *not* build libtalloc and instead look for it in the system path.  (If I
could get that working, we would use that solution for both libtalloc and
libtdb.)

> * you can decide to only link libtalloc statically by specifying
>   --with-static-libs=libtalloc

Doesn't actually work, as mentioned in my previous mail.

> * when you link libtalloc dynamically, you need to provide
>   libtalloc.so on systems that don't have it. it is installed
>   into the $LIBDIR folder by plain samba install. 

Actually, no; it has an soname, so what needs to be provided is
libtalloc.so.0.  The samba build rules are buggy in this regard as well,
since they install each lib under the "*.so" name, and we have to rename it
in the Debian packaging to get it under the right name for the runtime
linker.

>   so you can put it in the samba-common package (e.g.) or
>   build samba3's own libtalloc packages. (by cd'ing to
>   source/lib/talloc and building there).

These would never belong in the samba-common package.  We need packaging
that's future-proofed against ABI changes, so each shared library we ship
will get its own package.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org