<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
We generally have two sets of users:</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
1) Ones using the scripts installed from CPAN</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
2) Developers who may use the scripts directly</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
In case #1 I could see the benefits of using the perl version used for installation, as the dependencies should also be installed as well. Alternatively, in case #2 it makes sense to default to ‘/usr/bin/env’ to cover as many cases as we can. Case #1 is already
set up.</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
<br>
</div>
<div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">
chris</div>
<p class="airmail_on">On September 11, 2018 at 2:15:35 PM, Steven Lembark (<a href="mailto:lembark@wrkhors.com">lembark@wrkhors.com</a>) wrote:</p>
<blockquote type="cite" class="clean_bq"><span>
<div>
<div></div>
<div>On Wed, 29 Aug 2018 12:19:54 +0100<br>
Carnë Draug <carandraug+dev@gmail.com> wrote:<br>
<br>
> Hi<br>
> <br>
> I was wondering if there's any consensus about what should be used in<br>
> the shebang line. Looking at the existing scripts, I found:<br>
> <br>
> #!perl<br>
> #!/usr/bin/env perl<br>
> #!/usr/bin/perl<br>
> #!/usr/bin/perl -w<br>
> <br>
<br>
POSIX did away with non-absolute path #! lines.<br>
<br>
#!/usr/bin/perl is largely unusable as it assumes you are using the<br>
O/S installed versin of perl, which you usually aren't (unless you<br>
want to use 5.8 on Centos or 5.10 on Redhat or 5.16 on Amazon linux).<br>
<br>
Net result: "env" is the only sane way to go.<br>
<br>
Luvly thing is that env might be installed in /bin/env or /usr/bin/env<br>
depending on Linux vs. BSD vs. SysV roots of whatever you are running<br>
Perl on (let alone Windows...). <br>
<br>
The one most likely to work is:<br>
<br>
#!/usr/bin/env perl<br>
<br>
linux habitually installs env into /bin with a symlink in /usr/bin;<br>
BSD & SysV install it in /usr/bin maybe-without a symlink in /bin.<br>
<br>
I any case using "/usr/bin/perl" either ties you to decade(s) out of<br>
date perl with the O/S distro or forces you to update the disro perl,<br>
which may break ancient pieces of the distro itself.<br>
<br>
<br>
-- <br>
Steven Lembark 3920 10th Ave South<br>
Workhorse Computing Birmingham, AL 35222<br>
lembark@wrkhors.com +1 888 359 3508<br>
<br>
_______________________________________________<br>
Bioperl-l mailing list<br>
Bioperl-l@mailman.open-bio.org<br>
http://mailman.open-bio.org/mailman/listinfo/bioperl-l</div>
</div>
</span></blockquote>
</body>
</html>