> so that seems like a terrible idea that would achieve > the opposite result.
I respectfully disagree. Neither approach is universal or POSIX specified. So while I agree it can be left as-is since only a basic Bourne shell is needed, I would not just dismiss it/write it off as a terrible idea. There are reasons why #!/usr/bin/env is colloquially preferred to launch an interpreter in most shell script cases. For example, there are systems where /bin/sh is NOT a POSIX compliant shell. Alternatively, what if I have a different or compliant `sh` in my PATH, but not necessarily in /bin? This is not a scenario I made up, one can quickly research to see. I will not bikeshed the topic further, we can go either way, but I don't think it qualifies as a "terrible idea". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
