Samba4 on OpenBSD: a report (tags: waf, s3fs, ntvfs)
tnagy at waf.io
Mon Aug 31 19:11:33 UTC 2015
On Mon, 31 Aug 2015 17:41:32 +0200, (Jérémie Courrèges-Anglas) wrote:
> last week we (OpenBSD) have switched the net/samba package in our ports
> tree from latest Samba3 (+ patches) to Samba4 - samba-4.1.19 to be
> exact. The work on Samba4 was started by OpenBSD developer Vadim
> Zhukov, who did a big amount of work. The co-maintainers of this samba
> port are Ian (cc'd) and I.
> Here's a bit of feedback about the transition to samba4.
> One thing made the transition complicated: waf. The problem is that, as
> opposed to autotools that have been tested on and have knowledge of tons
> of environments, waf is young.
The Waf version that Samba is using is indeed young. The current Waf version is 1.8, not 1.5.
> Plus it encourages you to write custom
> code, which then breaks on "exotic" setups. This is the case on
> OpenBSD, where we use a traditional shared libraries naming scheme.
> Right now updating to samba-4.2.3 is not possible because of changes in
> this regard in samba 4.2.x. I'll try to discuss these problems in time
> with Samba developers that want to give a hand.
There was a long thread on this mailing list about OpenBSD. For some reason, it seems rather difficult to get build-script-related patches in Samba at the moment. I am still waiting on the following for example: https://bugzilla.samba.org/show_bug.cgi?id=11439
Feel free to contact me directly if you believe particular OpenBSD features should be have better support in Waf.
More information about the samba-technical