[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Explicit interpreter paths considered harmful
From: |
Ludovic Courtès |
Subject: |
Re: Explicit interpreter paths considered harmful |
Date: |
Thu, 29 Oct 2009 14:37:11 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Hi,
Paolo Bonzini <address@hidden> writes:
>> --- a/build-aux/gitlog-to-changelog
>> +++ b/build-aux/gitlog-to-changelog
>> @@ -1,4 +1,7 @@
>> -#!/usr/bin/perl
>> +#!/bin/sh
>> +# Accommodate systems where /usr/bin/perl is not the right path.
>> +exec perl -x "$0" "$@"
>> +#!perl
>>
>> The only assumption it makes is about /bin/sh, but that one seems to be
>> hard (impossible?) to avoid anyway.
>
> Yeah. But why not the standard
>
> #! /bin/sh
> eval 'exec /usr/bin/perl -S $0 ${1+"$@"}'
> if 0;
>
> suggested in perlrun(1)?
You mean without ‘/usr/bin/’, right? If so, then yes.
Thanks,
Ludo’.
- Explicit interpreter paths considered harmful, Ludovic Courtès, 2009/10/29
- Re: Explicit interpreter paths considered harmful, Paolo Bonzini, 2009/10/29
- Re: Explicit interpreter paths considered harmful,
Ludovic Courtès <=
- Re: Explicit interpreter paths considered harmful, Paolo Bonzini, 2009/10/29
- Re: Explicit interpreter paths considered harmful, Jim Meyering, 2009/10/29
- Re: Explicit interpreter paths considered harmful, Ludovic Courtès, 2009/10/29
- Re: Explicit interpreter paths considered harmful, Jim Meyering, 2009/10/29
- Re: Explicit interpreter paths considered harmful, Ludovic Courtès, 2009/10/29
- Re: Explicit interpreter paths considered harmful, Simon Josefsson, 2009/10/30
- Re: Explicit interpreter paths considered harmful, Ludovic Courtès, 2009/10/30
Re: Explicit interpreter paths considered harmful, Ludovic Courtès, 2009/10/29