03.06.2022 05:31, Andrew Bartlett wrote:
On Fri, 2022-06-03 at 13:08 +1200, Matt Grant wrote:
Otherwise, libwbclient0 ends up being installed when samba-lbs is
installed due to depending on samba-libs?
I read this like samba-libs uses libwbclient, not like libwbclient
uses samba-libs (would be wrong).
libwbclient0 should not depend on anything else in Samba (due to
licence requirements) so if there is a linking reason for this we
should check into this.
I did move one more library from samba-libs to libwbclient while
packaging 4.16 on debian.
Overall, this is the current content of libwbclient0.deb:
/usr/lib/x86_64-linux-gnu/libwbclient.so.0.15
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0.0.1
/usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0
/usr/lib/x86_64-linux-gnu/samba/libiov-buf-samba4.so.0
/usr/lib/x86_64-linux-gnu/samba/libreplace-samba4.so.0
/usr/lib/x86_64-linux-gnu/samba/libsamba-debug-samba4.so.0
/usr/lib/x86_64-linux-gnu/samba/libsocket-blocking-samba4.so.0
/usr/lib/x86_64-linux-gnu/samba/libsys-rw-samba4.so.0
/usr/lib/x86_64-linux-gnu/samba/libtime-basic-samba4.so.0
Some of these has been there before. Some (I think it was
just one, can't remember which) were added by me during
4.16 packaging time. One of my todo items about samba states
to review which libs are actually used by which binary and
move them between packages - somewhat similar to how I moved
files between samba-libs and python3-samba packages. When I
did 4.16 initially I didn't think much about that aspect, b/c
else we'd not have 4.16 now :)
Now when I looked at this, I don't see why libsamba-util.so is
in there at all. Maybe in 4.13 there was a reason for that,
I don't know the reason for it to be there for 4.16. The
rest (in /samba/) are ones used by libsamba-utils, it seems.
/mjt
There have been regressions in the past, so if only expressed in
packaging this might be historical.
