bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Explicit interpreter paths considered harmful


From: Eric Blake
Subject: Re: Explicit interpreter paths considered harmful
Date: Fri, 30 Oct 2009 06:38:52 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jim Meyering on 10/30/2009 6:29 AM:
>>>>> +eval '(exit $?0)' && eval 'exec perl -wS "$0" ${1+"$@"}'
>>>>> +  & eval 'exec /usr/bin/perl -wS "$0" $argv:q'
>> shouldn't that be perl, rather than /usr/bin/perl?
> 
> I could not arrange for that 2nd eval line to make a difference,
> so figured it'd be best to leave it as is.

Did you try: tcsh ./script?  I'm wondering if that second eval is catering
to users who run SHELL=tcsh, since the script no longer has a shebang, and
tcsh has different rules on how to attempt scripts that lack a shebang.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrq3lwACgkQ84KuGfSFAYAA1ACeL0rLLch18WmRn7gSbJRJPg69
6SQAoL1P3qybmVUHU39O910yqifaBa5j
=tN1g
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]