[Pkg-samba-maint] r1004 - in trunk: . patches
vorlon at debian.org
Tue Jan 31 13:57:39 UTC 2006
On Tue, Jan 31, 2006 at 01:28:50PM +0100, Peter Eisentraut wrote:
> Am Dienstag, 31. Januar 2006 01:48 schrieb Steve Langasek:
> > No, this is wrong. If you are using a proper soname, there is *no* reason
> > for this .so to exist; glibc should find it just fine under the name
> > /lib/libnss_winbind.so.2, which is the more appropriate name for it than
> > /lib/libnss_winbind.so. Please either kill the symlink and just install as
> > .so.2, or install the symlink and leave the upstream build rules alone. (I
> > prefer the first option, FWIW.)
> Obviously, there are about N! ways to set this up, none of which make too
> much sense, as evidenced by your two diametrically opposed solutions.
Huh? Both of these make plenty of sense. The path that glibc is going to
use when searching for the NSS module is libnss_<module-name>.so.2. The "2"
indicates the major version of the NSS interface (in theory), and this is
the only path that's relevant to the runtime environment. Now, glibc
installs its own NSS modules as /lib/libnss_<module>-<glibc-version>.so;
this matches the behavior of all of the libraries glibc installs, and I
suspect is done in order to reduce the danger of a partially unpacked
/lib/libnss_<module>.so.2 destroying the system. (Not really a problem for
Debian because dpkg already handles this for us, but anyway.) But there is
no reason for an unversioned /lib/libnss_<module>.so on the system.
So if the soname is libnss_winbind.so.2, there is no need for any symlink at
all and we should not create one. If the soname is libnss_winbind.so (which
isn't a very good soname, but it's the default upstream), then the symlink
for libnss_winbind.so -> libnss_winbind.so.2 *must* be included in the
package to fix this bug. But symlinking libnss_winbind.so.2 ->
libnss_winbind.so, when the soname is libnss_winbind.so.2, is just
> The current setup, however, is how other libnss modules are installed
> (namely, installed as .so, soname .so.2, symlink .so.2.).
Not any of the ones on my system. There are -2.3.5.so's, but that's it.
AFAICT, it would be inappropriate for nss_winbind to use -2.3.5 in its
filename since it's not part of glibc.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon at debian.org http://www.debian.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20060131/f2cb11c0/attachment.pgp
More information about the Pkg-samba-maint