Should we have programs with executable permissions in the distro
Lucian Branescu
lucian.branescu at gmail.com
Sun Aug 1 13:51:10 UTC 2010
2010/8/1 Alberto Simões <albie at alfarrabio.di.uminho.pt>:
>
>
> On 01/08/2010 14:34, Vasily Chekalkin wrote:
>>>> Does it have any disadvantage to set it from "#! perl" to
>>>> "#!/usr/bin/perl"?
>>>>
>>>> Also: "#! parrot" -> "#!/usr/bin/parrot"
>>>>
>>>> This is my favorite.
>>>
>>> Surely the #! for perl should be the path of the perl used to run Configure.pl,
>>> and the #! for parrot be the path parrot will be installed to?
>>>
>>> /usr/bin/perl and /usr/bin/parrot may not even exist.
>>
>> Indeed. What about "#!/usr/bin/env perl"? I'm not sure how it works on Windows.
>
> I really never understood how this one works :-|
I thought that was the canonical way to do it. All python scripts I've
ever seen had #!/usr/bin/env python. It's the option most likely to
run everywhere.
More information about the parrot-dev
mailing list