Re: trap commands in auxiliary scripts

On 5/29/26 22:55, Jan Engelhardt wrote:
> On Saturday 2026-05-30 02:58, Jacob Bachmeyer wrote:
>> [...]
>>
>> I posit that a better solution would be to add a test that our assumptions hold
>> to configure and bail out early on in a weird environment that would do things
>> like putting a single quote into $lockdir. Maybe packages using automake should
>> refuse to build in directories with absolute full names containing quote marks?
>>
>> Something like:  (in the generated configure)
>>
>>    case `pwd` in
>>       *[\'\"]*)
>>         echo "ERROR: cannot build reliably in a location named with quote
>>         marks"
>>         exit 1
>>         ;;
>>    esac
> There are likely more characters that can create problems down the line,
> e.g. everything that has a special meaning to make(1), like the
> space character U+0020 and the backslash itself.

I believe that space can be handled with proper quoting, but you have a 
good point about adding backslash to the list---many non-POSIX systems 
use it as a directory separator.


-- Jacob