From owner-freebsd-python@freebsd.org Tue May 21 21:26:03 2019 Return-Path: Delivered-To: freebsd-python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6895E158FE30 for ; Tue, 21 May 2019 21:26:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EEBC2818E4 for ; Tue, 21 May 2019 21:26:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AC253158FE2F; Tue, 21 May 2019 21:26:02 +0000 (UTC) Delivered-To: python@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89ACA158FE2E for ; Tue, 21 May 2019 21:26:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 216FC818E1 for ; Tue, 21 May 2019 21:26:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 58BAB1454F for ; Tue, 21 May 2019 21:26:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x4LLQ138085650 for ; Tue, 21 May 2019 21:26:01 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x4LLQ1Ng085642 for python@FreeBSD.org; Tue, 21 May 2019 21:26:01 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 237952] mail/notmuch: port still has build dependency python27 (transitive, via devel/talloc) Date: Tue, 21 May 2019 21:26:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: timur@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: koobs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2019 21:26:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237952 --- Comment #10 from Timur I. Bakeyev --- 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 l= eads 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 exter= nal WAF to build those ports. On a popular demand from embedded systems users I've added "hidden" NO_PYTH= ON flag to the related ports that disables building related Python bindings, w= hich 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 fo= und 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 versi= ons 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. --=20 You are receiving this mail because: You are on the CC list for the bug.=