Date: Sun, 28 Jun 2015 18:20:54 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Michael Gmelin <freebsd@grem.de>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>, python@FreeBSD.org, Marcus von Appen <mva@FreeBSD.org> Subject: Re: python_CMD in shebangfix.mk Message-ID: <558FAE66.4050101@FreeBSD.org> In-Reply-To: <20150628013453.3b38e871@bsd64.grem.de> References: <20150628013453.3b38e871@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28/06/2015 9:34 AM, Michael Gmelin wrote: > This has been discussed before on freebsd-python: > > http://lists.freebsd.org/pipermail/freebsd-python/2014-May/006964.html > > I just found myself writing > > python_OLD_CMD= /usr/bin/env python > python_CMD= ${PYTHON_CMD} > > as python_CMD is /usr/local/bin/python by default, which seems to be > against > > https://wiki.freebsd.org/Python/PortsPolicy > > which says > > "Executable scripts being installed MUST use ${PYTHON_CMD as shebang > line. See: Mk/Uses/shebangfix.mk" > > So > > python_CMD?= ${PYTHON_CMD} would seem a reasonable default. > > Also, adding "/usr/bin/env <language>" as an alternative > <language>_OLD_CMD would be useful. > > - Michael > This seems reasonable, I recall thinking a similar thinge thing last week. CC'ing python@ and mva@ who created that entry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?558FAE66.4050101>