> On Jun 12, 2019, at 4:47 PM, Bruce R Miller via macports-dev
> wrote:
>
> So, I tracked it down to the Makefile that perl's MakeMaker generates;
> an innocuous thing called "fixin" does that substitution.
Possibly related: it is a known issue in MakeMaker that `#!/usr/bin/env perl`
in
On 6/12/19 3:06 PM, Ryan Schmidt wrote:
On Jun 12, 2019, at 13:41, Bruce R Miller wrote:
On 6/12/19 1:14 PM, Ryan Schmidt wrote:
On Jun 12, 2019, at 10:26, Bruce Miller wrote:
So, apparently the perl portgroup replaces shebang
lines that it recognizes with a call to the specific
perl that
On Jun 12, 2019, at 13:41, Bruce R Miller wrote:
> On 6/12/19 1:14 PM, Ryan Schmidt wrote:
>> On Jun 12, 2019, at 10:26, Bruce Miller wrote:
>>
>>> So, apparently the perl portgroup replaces shebang
>>> lines that it recognizes with a call to the specific
>>> perl that was specified in the
On 6/12/19 1:14 PM, Ryan Schmidt wrote:
On Jun 12, 2019, at 10:26, Bruce Miller wrote:
So, apparently the perl portgroup replaces shebang
lines that it recognizes with a call to the specific
perl that was specified in the portfile (? is that right?)
And if so, it doesn't recognize the above
On Jun 12, 2019, at 10:26, Bruce Miller wrote:
> [This is motivated by the LaTeXML port,
> but is a general question about perl portgroup]
>
> A colleague suggested the clever shebang line
> #!/usr/bin/env perl
> as a way to easily allow testing against different
> versions of perl, running
* Bruce Miller:
> (And ideally, I'd avoid the whole version business, since LaTeXML
> *should* work with any version of perl after, I think, 5.10)
If you are able to determine a minimum required Perl version 5.x.y,
might adding 'use 5.x.y;' (e.g. via a patch) for a compile time version
check
[This is motivated by the LaTeXML port,
but is a general question about perl portgroup]
A colleague suggested the clever shebang line
#!/usr/bin/env perl
as a way to easily allow testing against different
versions of perl, running in sandboxes, etc.
This has worked fine on all systems, so far,
