Re: Topics currently in the Stalled category
- From
Jeff King <peff@peff.net>
- Date
- Nov 28, 2012, 03:12 UTC
- Message-ID
- <20121128031238.GC27772@sigill.intra.peff.net>
- In-Reply-To
- <CAMP44s3F4MPm-kLAW67rZG8oZg76CGS32h44LnK05UT11TOnSA@mail.gmail.com>
On Wed, Nov 28, 2012 at 04:10:07AM +0100, Felipe Contreras wrote:
Show 9 quoted lines
> >> Why generate it? There's nothing to generate. python's source code > >> needs regeneration, bash's code doesn't. > > > > We fix up the #!-lines on all of the existing shell scripts (as well as > > python and perl). Wouldn't we want to do the same for people who have > > bash in an alternate location? > > '#!/usr/bin/env bash' should take care of people who have bash in an > alternate location, no?
If that is where there env is. I do not recall offhand if that is a problem for anyone. Still, I don't think it is that big a deal to treat it like we do other scripts, and provide the usual boilerplate (which also gets us NO_BASH if you have an old or broken bash and want to skip the tests). I just sent a patch.
-Peff