On Tue, 2021-11-02 at 06:00 +0000, Vasyl Gello wrote: > Hi Andrew, > > 2 листопада 2021 р. 05:31:26 UTC, Andrew Bartlett <[email protected] > > написав(-ла): > >My recommendation is that someone works with us upstream to kill > samba- > >libs, which would reduce the set. It should be a SUBSYSTEM used by > the > >python module in the same directory only. > > > >Then work to disable the C->python bindings except in a selftest > build > >(we don't go C->python in production, only Python -> C). That will > >remove the problem once and for all. > > > >But do this upstream. > > Makes sense! What Helmut proposed is a perfect task for machine > learning but > moving files here and there without solution of root cause is a waste > of efforts. > > Basically, I am very new to Samba development. While I do understand > conceptually > what you recommend here, I'd like to understand the scope of work > needed in a > greater detail to plan my time carefully. Which part of Samba > documentation should > I read first on its architecture? It would be great to get a roadmap > for this epic so > we can find more people who can be involved in it.
I don't think this is an epic, but there is no architecture diagram. The build system is 'waf', which is wrapped into wafsamba, so unlike nothing you have seen before. You are likely to be eaten by a grue. I also misspoke, the lib to remove is samba-policy. Start with a simple patch to combine that. See https://wiki.samba.org/index.php/Contribute to start. Andrew Bartlett -- Andrew Bartlett (he/him) https://samba.org/~abartlet/ Samba Team Member (since 2001) https://samba.org Samba Team Lead, Catalyst IT https://catalyst.net.nz/services/samba Samba Development and Support, Catalyst IT - Expert Open Source Solutions
