my $target_dir = catfile $vars->{documentroot}, "util";
+ my $perl = catfile $Config{bin}, + (Apache::TestConfig::WIN32 ? 'perl.exe' : 'perl'); +
In that case, we do know the path to perl, it's stored in Apache::Build:
require Apache::Build; my $build = Apache::Build->build_config; my $perl_path = $build->perl_config('perlpath');
$Config{bin}/perl is definitely wrong, as it can be $Config{bin}/perl5.9.0 for example. Or anything else for that purpose. e.g. $Config{bin}/python to confuse the management ;)
Good point :) - a revised diff appears below using Apache::Build.
The patch didn't apply for me, but I've wrestled it in manually. Works fine for me!
I've done a few tiny tweaks and attached a version that applies cleanly (e.g. $perlpath can be retrieved at compile time).
+1 to commit. Great work, Randy!
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
diff
Description: application/java-vm
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
