On Jun 24, 2004, at 1:02 AM, Peter O'Gorman wrote:
Most of these packages allow the user to override their tests for perl
by checking the PERL environment variable first. If we just have fink
set PERL to /usr/bin/perl by default (different default for perl
modules, I guess), then the problem wil
On Jun 24, 2004, at 12:38 AM, David Brown wrote:
On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote:
More accurately probably,
#! `which perl`
#! /usr/bin/env perl
which will actually work. There are a lot of strange restrictions on
that line.
This was just symbolic notation, to stress that what
David Brown wrote:
On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote:
More accurately probably,
#! `which perl`
#! /usr/bin/env perl
which will actually work. There are a lot of strange restrictions on
that line.
Most of these packages allow the user to override their tests for perl by
check
On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote:
> More accurately probably,
> #! `which perl`
#! /usr/bin/env perl
which will actually work. There are a lot of strange restrictions on
that line.
Dave Brown
---
This SF.Net email sponsor
On Jun 23, 2004, at 10:57 PM, jfm wrote:
It is due to the fact that a number of pkgs install scripts beginning
with
#!/currently/active/perl
More accurately probably,
#! `which perl`
Cf all
'checking for perl... /sw/bin/perl'
in log files
JF
---
