On Tue, Jun 11, 2013 at 12:12 PM, Jerry <je...@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—those 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.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
