[Bug 237952] mail/notmuch: port still has build dependency python27 (transitive, via devel/talloc)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237952

--- Comment #10 from Timur I. Bakeyev <timur at FreeBSD.org> ---
That was interesting reading, thanks :)

So, you found most of the answers yourself, so let me summarize the current
state of the Samba development and related ports.

Samba 4.x up to 4.10 uses highly customized, but old version of WAF. That leads
to :

1. Hard dependency, at least on a build time, on Python 2.7 exclusively.
2. Inability to use external generic WAF.

There is no clean and easy way to use arbitrary Python version and/or external
WAF to build those ports.

On a popular demand from embedded systems users I've added "hidden" NO_PYTHON
flag to the related ports that disables building related Python bindings, which
allow you to have packages(on the price of losing AD functionality) without
Python 2.7 dependency. Still you'll need it for the build stage. But you found
that out yourself.

It's also possible to get Python3 bindings in ADDITION to Python2 ones, but
that would contaminate your system with the Python 2.7.

There is no clean way out of this legacy until Samba 4.10+, which is coming.

But that be a complicated process AFAIK, as we'd need to get parallel versions
of talloc/tevent/tdb/ldb ports with Python3 only dependency until Samba .49
will be phased out.

As for your problem with talloc in particular, there is a new talloc 2.2.1
release, which uses new Python3 dependent WAF(no, it's not compatible with
Python2, at least officially).

I have it in my tree and the only problem is how to name the port to keep, at
least for this year, parallel versions of the "old" and "new" ports.

Advice is welcome how to implement it gracefully.

-- 
You are receiving this mail because:
You are on the CC list for the bug.