>>>>> "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! - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Mon Jul 10 23:10:01 2006
This archive was generated by hypermail 2.1.8 : 2006-07-10 23:10:29 EST