Date: Wed, 17 Jan 2018 06:37:20 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224024] DEFAULT_VERSIONS for python and PYTHON_VERSION broken after r455210 (FLAVORS) Message-ID: <bug-224024-13-jB6hSyFAqV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224024-13@https.bugs.freebsd.org/bugzilla/> References: <bug-224024-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224024 David Naylor <dbn@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dbn@FreeBSD.org --- Comment #16 from David Naylor <dbn@FreeBSD.org> --- I would like to add my 2c on PYTHON_VERSION:=20 There are, I think, two situations where PYTHON_VERSION adds functionality = that FLAVORS does not provide: - if a port supports multiple versions of python but does not support FLAV= ORS (for example end user programs[1]).=20=20 - if a port supports multiple versions of python but is only a consumer of python (be it for building or for support scripts at runtime) In both these cases if someone wants to use a different version of python, without changing the default version of python, then PYTHON_VERSION is the recommended (and currently supported) way.=20=20 I do, however, think FLAVORS and PYTHON_VERSION need to be enhanced, specifically: - setting PYTHON_VERSION then forces the default FLAVOR, and - setting PYTHON_VERSION outside the range of FLAVORS gets that version ad= ded to FLAVORS Alternatively, we need to drop support for using using non-default versions= of python (and correctly handle when a port does not support a default version= ). [1] See the discussion around textproc/meld: https://lists.freebsd.org/pipermail/svn-ports-head/2018-January/165377.html --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224024-13-jB6hSyFAqV>