Re: Why MP2

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

On Thu, 16 Dec 2004, colin_e wrote:

> Thanks for the background Randy. I have seen ActiveState
> get a pretty major hammering in some quarters for their
> support of Perl , so it's interesting to get a more
> reaoned perspective.
>
> It's a real shame the mod_perl build can't be made
> hands-off, as it seems that would bring so many Apache::*
> modules on line with no extra effort, but if these can be
> made available on the uwinnipeg repository i'm more than
> happy to live with that ;-)

One could make it somewhat more automated by searching for
an Apache2 directory, and if one is found, prompting the
user if this is the one she/he wants to build mp2 against.
But one still needs the human interaction for this last
point to be successful in all cases, and I'd suspect the
automated build system would fail more often than not with
it. So it's probably not worth it.

Note that, once you know the options you want mod_perl to
use when building at the Makefile.PL stage, you can specify
these options for later builds in a makepl_args.mod_perl2
file, as described at
   http://perl.apache.org/docs/2.0/user/install/install.html

> Re:
>
> > It's odd that Windoze needs a .dll manually installed,
> > when on Unixes mod_perl.so is sufficient on its own.
>
> It wasn't the mod_perl.so I was querying, but-
>
> httpd.conf
> ----------
> LoadFile "C:/Prog/Perl/bin/perl58.dll"
>
> It's this bit that differs between the Win and Unix
> configurations, Solaris doesn't need a separate perl
> library configured on top of (actually prior to)
> mod_perl.so (presumably because it's found via the ld
> library path?)

Loading perl58.dll isn't always needed - it's suggested
to do so in order to specify which perl is being used, in
cases that one has multiple Perl installations on your
system and/or the PATH environment variable may not be set
to use the appropriate Perl that mp2 expects.

> There definately is a problem with installing mod_perl in
> a path with spaces at the moment. This was only a week or
> so ago for me but it's amazing how fast the memory goes
> when you're frying your brain trying to grapple with a ton
> of other software. From memory there were two distinct
> problems.
>
> One was a classic "C:\Program (sic) is not a valid program
> or batch file" type failure to execute a command. The
> other was more obscure, i'm struggling here but i'm pretty
> sure one piece that failed was the post-install script
> that downloads and installs the perl .dll, I think it
> couldn't find the Apache installation dir.

I'll take a look at the post-install script - thanks.

> Thanks for putting up the packages mentioned. I'm going to
> go away and try these now. What is the best method to give
> you feedback, direct mail or is there a formal feedback
> alias for the repository?

For questions/suggestions/problems about the repository,
you can email me privately.

        -- 
        best regards,
randy

-- 
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