From: Randal L. Schwartz <merlyn@stonehenge.com>
Date: Mon, 10 Jul 2006 13:09:25 GMT
Subject: Re: [Patch] Using 'perl' in *.sh
Message-ID: <86veq5sj22.fsf@blue.stonehenge.com>
In-Reply-To: <200607100741.26377.michal.rokos@nextsoft.cz>

>>>>> "Michal" == Michal Rokos <michal.rokos@nextsoft.cz> writes:

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

which *pointlessly* doesn't work if *I* have installed a private Perl and a
private git on a large shared systems, and *you* on the same system want to
use my git installation, but not necessarily have my Perl in your path.

There's *no* point to the env hack.  You're *installing* the file, which means
you can *rewrite* it as needed.  The env hack is a quick hack in case you have
a no-install file (something you're rsync'ing from one machine to another) for
strictly personal use.  Don't introduce that to something like the formal
git installation.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!