Re: dealing with executable shell scripts

[Nick Bowler]

On 2012-03-22 22:29 +0900, Miles Bader wrote:
> NightStrike <address@hidden> writes:
> > You are now saying that you want the source distribution to contain
> > files with execute permissions, but you still haven't explained how
> > you were doing that in your original example.
> 
> No I'm not.
> 
> I'm saying "I want there to be an executable version of the _destination
> script_ in my build [often the same as the source] tree, so the
> developer can say something like ./myscript in the build tree to test
> it."  In other words, I'd like my program to be usable in "uninstalled
> mode", kinda like Emacs is.  For normal executables, this is more or
> less the default state (if your program handles finding its data files
> etc, appropriately), and libtool goes to quite a bit of effort to make
> it work for dynamically linked executables; I'd like the same thing for
> script files.
> 
> My original example gave one way of doing this:  copy some "source file"
> to the destination executable script name, and make the latter
> executable.

FWIW, except for some details (for which I think you've already received
comments) your original approach seems fine to me, and is probably the
simplest and best approach to achieve what you want.

Cheers,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)