WAF 2.x upgrade for 4.9

Alexander Bokovoy ab at samba.org
Fri Jul 6 04:40:13 UTC 2018

On pe, 06 heinä 2018, Gary Lockyer via samba-technical wrote:
> Can I ask why the urgency to get the WAF upgrade into 4.9.  It's going
> to b much safer if this gets landed after the 4.9 cut-off.  My concern
> is that changing the build system this close to a release is going to
> cause all sorts of unnecessary pain.  Whereas if we wait until after the
> 4.9 release we'll have 6 months to sort out any issues.
Python 2 will be dropped by Python upstream in 2020. Postponing a
release to 2019 means we couldn't sort out distribution-wide Python 3
migration for Samba and Samba AD targets until first half of 2019. This
puts Fedora Project (in my case) into a dangerous state.

Waf upgrade is a first step in cleaning up Python 2 use and replacing it
with Python 3-compatible code. Unfortunately, a reality is that it takes
more than just porting Samba to py3 to do that. We need to make sure
distribution as a whole deals well with that -- for example, while
FreeIPA is using Python 3 already in Fedora 28 (current release) with
select Samba Python modules and there we can be sure things work, the
same couldn't be said for Samba AD path. Right now I couldn't even build
Samba AD with Python 3 to test whether things would work at all.

Note I'm talking about use outside of git master as we need to have
supporting libraries packaged with upgraded waf. We have ~2 months until
4.9 release, I think it is sufficient time to sort out waf issues in
prereleases given the analysis Andrew did to the resulting generated
config files.

/ Alexander Bokovoy

More information about the samba-technical mailing list