Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Jun 2013 09:17:53 +0200
From:      Baptiste Daroussin <bapt@FreeBSD.org>
To:        James <james@hicag.org>
Cc:        FreeBSD-ports <freebsd-ports@freebsd.org>
Subject:   Re: www/rubygem-passenger now requires bash?
Message-ID:  <20130620071752.GB23721@ithaqua.etoilebsd.net>
In-Reply-To: <CAD4099m3pMtQeyGVsbW6qMJSY=qwL5qq_Sg6ETpdj0_50eBTBg@mail.gmail.com>
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> <CAD4099m3pMtQeyGVsbW6qMJSY=qwL5qq_Sg6ETpdj0_50eBTBg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--KFztAG8eRSV9hGtP
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 11, 2013 at 02:03:13PM -0500, James wrote:
> On Tue, Jun 11, 2013 at 12:12 PM, Jerry <jerry@seibercom.net> wrote:
>=20
> > 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.
>=20
>     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=E2=80=94those start up =
with
>     a stock path unless you change /etc/rc or related.
>=20
>     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.
>=20

It is committed and available in the ports tree right now via: USES=3D sheb=
angfix.

But here it is another problem, apparently the reason for bash is that upst=
ream
expect it to parse .bashrc where they seems to recommand some people to put
configuration variables. IMHO, someone that knows a bit how passenger works
should contact them and tell them they could use for instance .profile inst=
ead
of .bashrc and always run /bin/sh instead of bash, I haven't dig the proble=
m at
all, but it doesn't seem like they really use bash only feature or anything
else.

regards,
Bapt

--KFztAG8eRSV9hGtP
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlHCrKAACgkQ8kTtMUmk6EwqsQCguXvtWsmSHeI9//8mPtU37Fzc
CMoAoJQou7XwwhE+EUNBcjdG4ggr3V2A
=dnSr
-----END PGP SIGNATURE-----

--KFztAG8eRSV9hGtP--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130620071752.GB23721>