<!DOCTYPE html><html><body>Hi Andrew,<br><br>2 листопада 2021 р. 05:31:26 UTC, Andrew Bartlett <abartlet@samba.org> написав(-ла):<br>>My recommendation is that someone works with us upstream to kill samba-<br>>libs, which would reduce the set. It should be a SUBSYSTEM used by the<br>>python module in the same directory only.<br>><br>>Then work to disable the C->python bindings except in a selftest build<br>>(we don't go C->python in production, only Python -> C). That will<br>>remove the problem once and for all.<br>><br>>But do this upstream.<br><br>Makes sense! What Helmut proposed is a perfect task for machine learning but<br>moving files here and there without solution of root cause is a waste of efforts.<br><br>Basically, I am very new to Samba development. While I do understand conceptually<br>what you recommend here, I'd like to understand the scope of work needed in a<br>greater detail to plan my time carefully. Which part of Samba documentation should<br>I read first on its architecture? It would be great to get a roadmap for this epic so<br>we can find more people who can be involved in it.<div style='white-space: pre-wrap'>-- <br>Vasyl Gello<hr>Certified SolidWorks Expert<br><br>Mob.:+380 (98) 465 66 77<br><br>E-Mail: vasek.gello@gmail.com<br><br>Skype: vasek.gello<hr>호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다</div></body></html>