Date: Wed, 30 Oct 2019 01:33:17 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 241463] [NEW PORT] devel/scons-py3: scons for python3 Message-ID: <bug-241463-21822-93bJpiQ4ZA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241463-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-241463-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 --- Comment #9 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Sunpoet Po-Chuan Hsieh from comment #6) This is the better option. The scons port should do nothing but declare the versions *it* supports, and scons consumers ought to declare specifically the version(s) they support, allowing them to move forward at their own pace, without 'imperative' selection by the framework. Notes: - It's worth considering having scons.mk support <version-specifier> in the exact same way that USES=python supports it, rather than it being an FLAVOR argument (scons:py27) This allows, scons consuming ports to declaratively specify/declare version support, rather than 'imperatively' 'choosing' a framework specific implementation details (flavor) This also enables / gives us the ability to factor out a generic <version-specifier> support across more areas of the framework, starting with Python / Scons, and improving it in the process ("!=X" support, "X,Y" support, etc), which has huge benefits for consistency and version derivation across our tree. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241463-21822-93bJpiQ4ZA>