config/conf.pl starts with '#!/usr/bin/perl', so it
will run only on sites which have perl in /usr/bin.
Some have it in /usr/local/bin, on some it's in even weirder places.
The following trick fixes that, using /usr/bin/env (which is available on all Unices I know of) to
find perl in the environment, and invoke it:
#! /usr/bin/env perl
# Invoke perl without making assumptions about
# its location
Logged In: YES
user_id=40435
Will release in 1.2.2.
Logged In: YES
user_id=40435
The bug you reported has already been fixed in CVS.
Please pull the latest version of your development tree from CVS.
If for some reason your problem still exists, please submit
another bug with this information.
Thank you for your help!
Logged In: YES
user_id=9941
Another fix is to place a symlink in /usr/bin to whichever version of Perl
is current. /usr/bin/perl is common enough on most *nix systems with Perl
that this shouldn't be a real problem.
I really don't like the env
hack, because it will still fall apart if Perl isn't in your path. How do
other projects deal with this issue? I'm sure it's a more widespread
problem.
Bron.
Logged In: YES
user_id=9941
Ahh, sorry - I notice that 'man perlrun' actually suggest using the env hack -
but it still feels very ugly.
Another (though also messy) solution is
to run 'which perl' during the install process and patch the conf.pl
file.
Bron.