Date: Tue, 20 Oct 2015 00:41:07 +0300 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Eitan Adler <lists@eitanadler.com> Cc: "ports-committers@freebsd.org" <ports-committers@freebsd.org>, "svn-ports-all@freebsd.org" <svn-ports-all@freebsd.org>, "svn-ports-head@freebsd.org" <svn-ports-head@freebsd.org> Subject: Re: svn commit: r399684 - in head: Mk/Uses astro/weather audio/lollypop audio/mma audio/pulseaudio audio/py-tagpy audio/ripit audio/sphinx chinese/pyzy chinese/ydict databases/luadbi databases/nagios-c... Message-ID: <20151019214107.GE47267@hades.panopticon> In-Reply-To: <CAF6rxg=oRUPOWvxfm=1AUxOuYFL3h-te-pbLBPZkadGB-iZLdw@mail.gmail.com> References: <201510191450.t9JEoqln023397@repo.freebsd.org> <CAF6rxg=oRUPOWvxfm=1AUxOuYFL3h-te-pbLBPZkadGB-iZLdw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Eitan Adler (lists@eitanadler.com) wrote: > > Log: > > Improve shebangfix framework > > ... > > > - Add more default values, such as "/usr/bin/env foo" for python, perl, bash, ruby and lua > > This seems like unexpected behavior. /usr/bin/env foo will call foo > depending PATH which is almost certainly what the author intended. > Fixing absolute references from /usr/bin/foo to another absolute path > or to being called via env makes sense. In almost all cases, author intended to just call `foo' without having to deal with a headache of different paths on different systems. If there is real life case where PATH handling is specifically needed, I'd like to see it. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151019214107.GE47267>