[Samba] classifying samba componens and sorting into debian binary packages

[Andrew Bartlett]

On Sat, 2024-05-25 at 18:00 +0300, Michael Tokarev via samba wrote:
> 25.05.2024 17:39, Michael Tokarev via samba wrote:
> > ====================   samba-common-bin - common binaries in
> > /usr/bin:       net       testparm - it probably should come
> > together with smb.conf but ok       nmblookup - should it be part
> > of smbclient? Probably irrelevant at this time.       samba-tool -
> > is about AD, I plan to move it to samba-ad-client pkg.       samba-
> > regedit - should it be part of the file server?       smbpasswd -
> > should it be part of the file server? But I guess it can be
> >           used to change password on another server too, so let it
> > stay.           Or should it be part of smbclient?      
> > dbwrap_tool - should it be part of ctdb?       samba-log-parser
> 
> There's also /usr/sbin/samba_kcc in there, - should go either to
> samba-ad-clientor samba-ad-dc, I can't understand which one.

samba-ad-dc
> >      also a few rpcd daemons used by samba and winbindd:      
> > /usr/libexec/samba/rpcd_*.
> >      samba-common-bin is not used by smbclient or libsmbclient (but
> > samba-common is).
> >      This package used to depend on python components (due to
> > samba-tool), but     with it moved elsewhere, python is not longer
> > needed.
> >      Just with samba-common-bin and winbind it should be possible
> > to join a     linux system to a domain (including AD, b/c `net ads
> > join`) and do user     auth without using remote files, or maybe
> > cifs-clients can be used for that too.
> > ====================   smbclient - client for the file server:
> >       smbclient, rpcclient, smbcacls, smbget, smbspool, smbtar, ...
> 
> Actually maybe whole samba-common-bin isn't really necessary,and all
> remaining files can be moved to smbclient (with it beingrequired by
> the file server).  samba-common-bin is a badly namedpackage which has
> its own functionality which is partly related tosmbclient, and it
> also has unrelated-to-client files which are usedby server packages
> (samba and winbind).
> > .....  On the otherhand, there are a few commands
> > (samba_downgrade_db, samba_upgradedns) which don'tfit neither in
> > samba (due to python deps and not being relevant to
> > standaloneserver use case) nor in samba-ad-client package (due to
> > being impractical withoutthe file server component).

These are part of samba-ad-dc, as are samba_dnsupdate, samba_spnupdate
> > I don't see how it can be split better.  Maybe an interesting way
> > would be tomove some files to samba-ad-dc and rename it to samba-
> > ad, so that it can be usedeither as a domain controller or a member
> > server.  In this case things likesamba_downgrade_db will go there. 
> > Or maybe just introduce samba-ad pkg whichdepends on samba and
> > samba-ad-client, and includes python-based ad-specificfile server
> > components.
> > BTW, do we really need samba_downgrade_db these days?  Changing
> > format to theone used by samba 4.7, srsly?  I'd just remove this
> > one :)
> 
> Both samba_downgrade_db (if this one is really needed still)
>  and samba_upgradedns(I found a reference to it in the wiki) can be
> part of samba-ad-dc package.Maybe together with samba_kcc (if it is
> not going to samba-ad-client).



You don't need to package samba_downgrade_db.
Thanks for giving this a try!
Andrew Bartlett
-- 
Andrew Bartlett (he/him)       https://samba.org/~abartlet/Samba Team Member (since 2001) https://samba.orgSamba Team Lead                https://catalyst.net.nz/services/sambaCatalyst.Net Ltd
Proudly developing Samba for Catalyst.Net Ltd - a Catalyst IT group
company
Samba Development and Support: https://catalyst.net.nz/services/samba
Catalyst IT - Expert Open Source Solutions