<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>
<blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">
<span>
<div>
<div><br>
<font color="#000000"><span style="caret-color: rgb(0, 0, 0);">...</span></font><br>
><br>
> The point is don't assume that you know more about how someone else<br>
> manages their Perl distributions than they do, or that packaging<br>
> approaches for Debian are suitable for all distributions of Linux,<br>
> Unix, and VMS.<br>
<br>
We are using MakeMaker for installation and it's MakeMaker that's<br>
setting the shebang. If you want the shebang to be "env", then set<br>
PERL_MM_SHEBANG=relocatable for the installation.<br>
<br>
Any change to this logic, can't be unique to the bioperl project and<br>
will be better discussed in MakeMaker and other toolchains used for<br>
installation.<br>
<br>
Carnë</div>
</div>
</span></blockquote>
</div>
<p>Just so it’s noted for the record, I agree with this. I really don’t want to go down the road of forging a bioperl-specific way of doing things, the current bioperl code base has tons of examples of this already. </p>
<p>It’s also worth noting that we’ve very rarely (if ever) had complaints about issues with scripts related to specific perl paths in the past. That doesn’t mean problems have never occurred, but it does suggest that it’s never risen to the point over the
years that someone has complained about it. All Carnë wants to do is standardize this.</p>
<p>chris</p>
<div></div>
</body>
</html>