Re: Proper handling of shebang line while performing local testing?

[Corion]

Maybe that someone was wrong.

You should have the perl (or whatever program) in the hashbang line which is used by the kernel to run the subsequent code. For shell scripts that is /bin/sh (or whatever), and for Perl scripts, that should resolve to the appropriate Perl interpreter.

Using the redirection through /usr/bin/env is en vogue with some people, but hardcoding /usr/bin/perl if that's not your Perl is just wrong.

[nysus]

Well, I've been googling around and it seems that the best practice for cpan modules is to use `/usr/bin/perl` and it will be replaced when the user installs the module. This is the best explanation I found on the matter: https://github.com/duncs/clusterssh/issues/45#issuecomment-153898849

[Corion]

Maybe then you need to invoke your tests in a different way. I usually run single tests as

perl -Mlib -w t/01-api.t

... and the whole test suite with

make test

or, if I want to run the author tests as well, with:

make
prove -bl xt/ t/

Directly starting a test will get things confused because the kernel will invoke the Perl that is hardcoded in the first line instead of using the Perl that you (may) want.