in reply to Why can't mod_perl+Mason just work?
Fedora comes with Apache 2 and even mod_perl pre-installed. However, HTML::Mason won't work with Apache2 and neither will Apache::Template, the closest alternative.
One thing to note, is that mod_perl for Apache2 is still beta. I don't know why FC doesn't come with Apache 1.3 anyway, because on linux, the advantages of Apache 2 (threads) are hardly worth the upgrade, IMO. At the very least it should offer both apache 2 and apache 1.3.
Anyway, in the past I've had enough trouble with the standard (pre - 2.0) mod_perl rpms from RedHat that I always build my own binaries there.
Re-installing Apache to get 1.3 is non-trivial for me and in any case doesn't address the real issue: the Perl web development community, rather than just doing their own thing (mod_perl, Mason, Template::Toolkit), need to seriously address usability.What usability are you talking about? You haven't installed anything yet. I run debian, and doing apt-get install apache-perl will install a nice apache 1.3 binary with mod_perl, which just works (tm).
Running perl -MCPAN -e'install Apache::Request' also works automatically.
update: indented
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Why can't mod_perl+Mason just work?
by gunzip (Pilgrim) on Aug 12, 2004 at 14:29 UTC | |
by Joost (Canon) on Aug 12, 2004 at 14:44 UTC |