"Shebang" lines for scripts on Patas
Here are the proper script headers for various interpreted languages on patas.
(Note: The distribution perl at /usr/bin/perl does not have the linguistics-specific modules installed.)
When developing scripts in other environments with final testing (and submission of homework) on patas, you may find that your development environment has the desired script binary in one place, and patas has the script binary in another. For example, you need to manually edit the shebang line on your perl scripts every time you move the perl script to patas. One way to get around this is to use /usr/bin/env
to find the path for your target script program, in this case perl.
For example, you may see the following for the location of perl 5.10 on patas and your devel machine:
jscott42@patas:~$ which perl
jscott42@patas:~$ perl --version
This is perl, v5.10.0 built for x86_64-linux
mymachine (hani-winxp): /usr/bin/perl
jeffry@hani-winxp ~ $ which perl
jeffry@hani-winxp ~ $ perl --version
This is perl, v5.10. (*) built for i686-cygwin-thread-multi-64int
(with 12 registered patches, see perl -V for more detail)
Replace your shebang line in your perl scripts to read:
and the local path for perl will automatically be substituted.
If you use this technique with Condor, you must
getenv = true
in your Condor submit script; otherwise there won't be a valid PATH
variable for /usr/bin/env to work with.
NB: to make sure you are using the same version of perl in both environments, run which perl
on each. If your devel version of perl doesn't match the version on patas, fiddle with your PATH
environment variable so the proper version is found, or create a link in your local /bin
, or /usr/local/bin
to the proper version of perl on your devel machine.
Use of /usr/bin/env
is a Good Thing in shebang lines, as it eliminates a lot of manual changes when doing cross-platform script development. And yes Virginia, it will work fine for python and ruby as well.