Date: Sat, 17 May 2014 13:33:44 +0400 From: Dmitry Sivachenko <trtrmitya@gmail.com> To: Marcus von Appen <mva@FreeBSD.org> Cc: python@FreeBSD.org Subject: Re: Wrong python_CMD in shebangfix? Message-ID: <9A0AFE0A-8150-41F9-962F-274D2C7A5694@gmail.com> In-Reply-To: <E04D7426-A04C-4609-87C7-B789B9E8E6A7@gmail.com> References: <0AE311F0-87F8-4376-8E24-742C6C54F564@gmail.com> <20140515053140.GA920@medusa.sysfault.org> <E04D7426-A04C-4609-87C7-B789B9E8E6A7@gmail.com>
index | next in thread | previous in thread | raw e-mail
Well, so what is the consensus on this? May I commit the proposed patch? On 15 мая 2014 г., at 10:46, Dmitry Sivachenko <trtrmitya@gmail.com> wrote: > > On 15 мая 2014 г., at 9:31, Marcus von Appen <mva@FreeBSD.org> wrote: > >> On, Wed May 14, 2014, Dmitry Sivachenko wrote: >> >>> Hello! >>> >>> Imagine that I have python-2 as default version, so that /usr/local/bin/python points to python2.7 >>> And I have a port which USE_PYTHON=3 and USES=shebangfix. >>> >>> It will "fix" python path as "/usr/local/bin/python" which is wrong (it should point to python3). >>> >> >> The path is not *wrong*. lang/python installs /usr/local/bin/python. >> > > I know, but in my example it would point to python2.7, rather than expected python3.3 which is wrong. > >help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9A0AFE0A-8150-41F9-962F-274D2C7A5694>