Re: Why MP2

[prev] [thread] [next] [Date index for 2004/12/15]

Further to this, I went looking at the specific case of 
Apache-CGI-Builder. I was hoping to
use the CGI::Builder framework, and was disappointed to find that the 
Apache handler i/f
was not available.

Sure enough, the ActiveState module status list-

    http://ppm.activestate.com/BuildStatus/5.8.html

shows Apache-CGI-Builder as unavailable.

Having looked into it, this is a pure perl module and really should work 
without
problems. The issue is a simple package dependency on mod_perl. The actual
error ActiveState failed on is-

	failed building Apache-CGI-Builder prerequisite mod_perl
	aborting build of Apache-CGI-Builder: failed prerequisites


Now mod_perl is installed on my machines, but the way Apache sets up
the lib path, mod_perl is not in the  default @INC. I.e. it's not in-
C:\Prog\Perl\lib\mod_perl, but in C:\Prog\Perl\lib\Apache2\mod_perl.

You have to say-

    use Apache2();
    use mod_perl;

in scripts to select the Apache2 libraries instead of Apache1.

Is it really this trivial problem that is preventing Apache-CGI-Builder
(and maybe a host of other Apache packages) from being available as PPMs?

There is no "make" by default on a vanilla Windoze box, so without a PPM
package the only alternative is a manual extract/copy operation. I will
try this but I will miss out on documentation etc.

Ideas on how to fix this? Maybe I am oversimplifying things, but if, 
say, changing a
dependency from "mod_perl" to "mod_perl || Apache2/mod_perl" would make a
whole bunch of (at least the pure perl) packages available via PPM this 
would be a
big gain for little pain.


Regards: Colin


colin_e wrote:

> I have recently switched to using ActiveState perl on my production 
> Solaris box as well as on my
> Windows machine for several reasons, including the fact that it's 
> considerably easier to get PPM
> working under ActiveState.
>
> However a big disappointment when I went looking for modules was the 
> sorry state of
> Apache::* modules under ActiveState's PPM.
>
> Take a look at http://ppm.activestate.com/BuildStatus/5.8.html and you 
> will see a sea of red
> for almost all the Apache modules. This is a real shame because there 
> are some fundamental
> building-block modules, like all the ApacheAuth* and most of the 
> session modules down here as
> broken.
>
> I don't have a handle on the Apache/Perl structure at the moment, but 
> I would expect there to be a
> couple of critical functions or interfaces at the root of this. Crack 
> those and half the list changes to
> "available". Dan mentioned libapreq2. Is this one of those critical 
> dependencies?
>
> Regards: Colin
>
>>>> In preparation for the upcoming release of mod_perl2, I'd like to 
>>>> prepare a list of reasons why a person/company would look at using 
>>>> mod_perl2, specifically, why upgrade from mod_perl1, and converting 
>>>> from other technologies.  So with that, what reasons do you have 
>>>> for wanting MP2? What prevented you from upgrading before?
>>>> What key features are most interesting for you?
>>>> How will this help your company?
>>>
>>>
>
>


        -- 
        Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html