Hi Michael! OK, see what you are thinking.
Was planning to do just what you did. Bins into samba-common-bin, libs into samba-libs. My bad about samba-dcerpcd.8 man page. Maybe ksmbd support should be started with all needed bins in samba-common-bin, and systemctl disabled ksmbd/samba-dcercpd service file(s) in samba package or elsewhere. Some smb.conf settings are specially needed for ksmbd apparently (samba-dcerpcd.8 manpage) Regards, Matt Grant On Tue, 14 Jun 2022 at 02:03, Michael Tokarev <m...@tls.msk.ru> wrote: > 13.06.2022 12:12, Matt Grant wrote: > > Hi Michael! > > > > For the libraries to move from the samba package, just used the > following command on each rpcd binary in /usr/libexec/samba: > > > > dpkg -S `ldd rpcd_epmapper | grep samba | cut -f 1 -d ' '` > > I suspected it was something like that. > > The problem here is that the two libs you moved from > samba to the new dcerpc package, are also used by the > samba package itself. By moving stuff like this, it > is too easy to create a circular dependency, which we > had quite a few in the past. I placed libs into the > samba package (and to winbind package and some other > cases) *only* when those libs are used by those packages > and not by other packages. The rest of libraries - > the ones which are used by more than a single package - > goes to samba-libs. Again, maybe I'm wrong there. > > Just thought that these libs which are used by a single > package *now*, may be used by more than a single package > in the future, and I should have a way to check for that, > maybe similar to how I check for unneeded inter-package > deps in d/rules already, but for more packages. > > BTW, you forgot the manpage for samba-dcerpcd. > > For now I moved the executables into samba-common-bin > and the two libs into samba-libs. Let's see how it will > be, maybe we'll create a new package for it. > > Thank you for the work and for the inspiration! > > /mjt >
