hummmmmmm

i tried to hack the code in RegistryCooker.pm and i saw that the files
differ from FreeBSD to Debian

let's look

Freebsd:

/usr/local/lib/perl5/site_perl/5.8.6/mach/Apache2/ModPerl/RegistryCooker.pm
sub can_compile {
    my $self = shift;
    my $r = $self->{REQ};

    unless (-r $r->my_finfo && -s _) {
        $self->log_error("$self->{FILENAME} not found or unable to stat");
        return Apache::NOT_FOUND;
    }

    return Apache::DECLINED if -d _;


Debian:
/usr/lib/perl5/Apache2/ModPerl/RegistryCooker.pm
sub can_compile {
    my $self = shift;
    my $r = $self->{REQ};

    unless (-r $r->filename && -s _) { 
        $self->log_error("$self->{FILENAME} not found or unable to stat"); 
        return Apache::NOT_FOUND; 
    }


HUMMMMMMMMMMMMM that's not the same source, but i dont really
understand, the mod_perl is the same version for the to systems......!
mod_perl/1.999.20

why on one it's $r->filename and on the other one is it $r->my_finfo ?????

should I notice the Debian Guys to change it or not ?
is it safe to play in this code? when i'll update my packages, i'll
lost the change....

thanks to you Stas for the tricks.. but... this is a problem.... will
others like this one surprise me?

thanks for all the help! 
Bruno Lavoie

Reply via email to