Re: samba4 libnss_winbind.so and libnss_wins.so symlinks PLIST failure

["T K Spindler (moof)" <dogcow%babymeat.com@localhost>]

On Thu, Jan 04, 2024 at 10:09:35AM +0100, Dr. Thomas Orgis wrote:
> 
> samba4$ grep libnss PLIST*
> PLIST:lib/libnss_winbind.so
> PLIST:lib/samba/private/libnss-info-samba4.so
> PLIST.Linux:lib/libnss_winbind.so.2
> PLIST.Linux:lib/libnss_wins.so
> PLIST.Linux:lib/libnss_wins.so.2
> 
> Does that make sense? Is libnss_winbind.so _not_ a symlink on NetBSD?
> Is a dangling link being installed?

It is not a link on my NetBSD 10_RC2 system:
-rwxr-xr-x  1 root  wheel  414528 Nov 16 10:04 /usr/pkg/lib/libnss_winbind.so

If you look at the unpatched sources for
samba-4.19.3/nsswitch/wscript_build you can see that the build
process creates the lib with wildly different names depending on
the OS; why samba has decided that linux really needs the lib as
libnss_winbind.so.2 on linux but libnss_winbind.so.1 on FreeBSD and
libnss_winbind.so on NetBSD, I could not tell you.

That said - I'm not sure how long this has been broken on Linux; 
it's weird that the Linux .so.2 <- .so symlink doesn't exist at all
in the build.