Date: Tue, 11 Jun 2013 14:03:13 -0500 From: James <james@hicag.org> To: FreeBSD-ports <freebsd-ports@freebsd.org> Subject: Re: www/rubygem-passenger now requires bash? Message-ID: <CAD4099m3pMtQeyGVsbW6qMJSY=qwL5qq_Sg6ETpdj0_50eBTBg@mail.gmail.com> In-Reply-To: <20130611131221.3a222e13@scorpio> References: <DFDFB371-63D0-430F-8E4E-77119578DDD8@gromit.dlib.vt.edu> <71c953f9ebbd220a72258fb1dbf322f8.squirrel@mouf.net> <CAF6rxg=zVwkdmW%2B_2UhSvk_e529Z0r=fL7EJHj6ezu41cJJAvw@mail.gmail.com> <20130611131221.3a222e13@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 11, 2013 at 12:12 PM, Jerry <jerry@seibercom.net> wrote:
> I totally agree. Plus, perhaps the port can be modified to use "env"
> to locate bash; ie, "\usr\bin\env bash". I use it all the time for
> shell scripts that I write for various systems and it hasn't failed
> me yet.
Aye. bapt@ is working on a solution for this. I'm not sure where
it's at right now, but it looks really handy. He's proposing a
framework that automatically fixes the path in shebangs. It's less
fragile than env(1) when dealing with daemons=97those start up with
a stock path unless you change /etc/rc or related.
I run into this problem sometimes too. I build ports to a
non-standard prefix so anything that hard-codes /usr/local is
apparent. :) At the moment I patch or substitute the scripts which
works fine, but bapt's solution is better.
--
James.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD4099m3pMtQeyGVsbW6qMJSY=qwL5qq_Sg6ETpdj0_50eBTBg>