Re: [Patch] Using 'perl' in *.sh

[Michal Rokos <michal.rokos@nextsoft.cz>]

Hi,

On Sunday 09 July 2006 22:33, Junio C Hamano wrote:
> Invocation of perl _in_ scripts can be controlled by user's
> PATH, but #! cannot be.  As Merlyn says 'env' is a nice hack,
> but we configure the scripts we install to have #!  pointing at
> the right interpreter as a more cleaner (than using 'env', that
> is) workaround anyway, so #! pointing at PERL_PATH and scripts
> relying on user's $PATH would be the right thing to do.

I don't se the point. If you ask me, I'd say it should be either:
- controlled fully via env: which means 'perl' in scripts and /usr/bin/env in 
*.perl; or
- set during install: which means 'full perl path' in scripts as well as in 
*.perl

Any mixture of above makes no sence to me. I'm afraid that any consensus will 
be hard to reach, but I don't see any other way round. (Well maybe some git 
specific exec wrapper to come over some broken 'env' commands)

M.

-- 
Michal Rokos

NextSoft s.r.o.
Vyskočilova 1/1410
140 21 Praha 4
phone:  +420 267 224 311
fax:    +420 267 224 307
mobile: +420 736 646 591
e-mail: michal.rokos@nextsoft.cz