On Jul 22, 2009, at 2:56 PM, Jonathan Swartz wrote:
> Yes, sorry about this - Mason's handling of mod_perl,  
> Apache::Request, etc. dependencies is pretty tortured, as the last  
> time anyone worked on it mod_perl 2 was still in flux.
>
> It would be great to tear that stuff out and replace it with  
> something a lot simpler, like HTTP::Engine. Mason really should not  
> have to know about mod_perl vs. fastcgi at this point.
>
> But yes, to get around this in the short term, you should just go  
> ahead and install Mason, ignoring the prereq.
>

Jon,

thank you for the response. I followed your advice, ignored  
Apache::Request, and I am now up and running with RT, HTML::Mason and  
mod_perl2.

        --ravi



> Jon
>
> On Jul 22, 2009, at 11:45 AM, ravi wrote:
>
>> On Jul 22, 2009, at 12:41 PM, I wrote:
>>> Hello all,
>>>
>>> I have scanned through the list archives, checked out the online
>>> docs (http://www.masonhq.com/?ApacheModPerl2, etc), and I am still
>>> lacking clue on how to solve the problem described below.
>>>
>>
>>
>> I dug around a bit more, and found the below in Build.PL:
>>
>>    my $has_mod_perl_2 = eval { require mod_perl2 } || 0;
>>    my $has_only_mp2 = ! $has_mod_perl_1 && $has_mod_perl_2;
>>
>>    # XXX - this really isn't right since we really want to know which
>>    # version of mod_perl they _intend_ to use with Mason, rather than
>>    # just blindly adding all these prereqs.
>>    if ($has_mod_perl_1)
>>    {
>>        $prereq{'Apache::Request'} = 1.05; # minimum for OSX
>>    }
>>
>> So, it looks like this is a well known issue. The question of why
>> Apache::Request refuses to install (because of mod_perl vs mod_perl2)
>> is still open, but I was hoping to bypass that and install
>> HTML::Mason, but it looks from the above I cannot, unless I ignore  
>> the
>> missing prerequisite.
>>
>>      --ravi
>>
>>
>>> I am trying to upgrade RT from 3.6.3 to 3.8.4 on a Gentoo box
>>> running Apache2, with both mod_perl and mod_perl2 installed, as well
>>> as a mix of Perl modules in vendor_perl and site_perl that
>>> occasionally conflict (I mention this since this could very well be
>>> the source of my problem!).
>>>
>>> One of the requirements for RT 3.8.4 is a newer HTML::Mason >= 1.36.
>>> When I try to upgrade HTML::Mason, it tells me that Apache::Request
>>> is a prerequisite. When I try to install Apache::Request
>>> (libapr-1.34) that errors out at test:
>>>
>>> t/apreq/big_input....# Failed test 1 in t/apreq/big_input.t at  
>>> line 40
>>> t/apreq/big_input....NOK 1# Failed test 2 in t/apreq/big_input.t at
>>> line 40 fail #2
>>> t/apreq/big_input....NOK 2# Failed test 3 in t/apreq/big_input.t at
>>> line 40 fail #3
>>> t/apreq/big_input....NOK 3# Failed test 4 in t/apreq/big_input.t at
>>> line 40 fail #4
>>> t/apreq/big_input....NOK 4# Failed test 5 in t/apreq/big_input.t at
>>> line 40 fail #5
>>> <so on>
>>>
>>> That's because:
>>>
>>> [Wed Jul 22 12:38:19 2009] [error] [client 127.0.0.1] failed to
>>> resolve handler `TestApReq::big_input':
>>>  Can't locate object method "boot" via package "mod_perl" at
>>>  /usr/lib/perl5/vendor_perl/5.8.7/i386-linux/Apache/Table.pm line 6.
>>>
>>> Problem seems to be the use of mod_perl, rather than mod_perl2.
>>>
>>> I installed Apache2::Request (libapr2) as well, but HTML::Mason
>>> still insists that Apache::Request is a prerequisite.
>>>
>>> I have looked through the HTML::Mason code and see checks for Apache
>>> vs Apache2, but those don't seem to be working as I thought they
>>> might.
>>>
>>> What am I doing wrong?
>>>
>>> I don't mind using CGI instead of mod_perl2/Apache2::Request, but I
>>> want to make sure that I am doing the right thing before I force
>>> install HTML::Mason.
>>>
>>> Thank you,
>>>
>>>     --ravi


------------------------------------------------------------------------------
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users

Reply via email to