[Catalyst] Perl Flavors (was PPM vs CPAN)

[Hugh Lampert]

Carl Franks wrote:
> You may want to look into Vanilla / Strawberry perl as an alternative
> to ActivePerl.
> It includes the mingw (gcc) compiler and nmake, and the perl included
> is compiled from scratch with mingw, rather than ms compilers.
>
Thanks, I will look into this for my next project.  I'm pretty married 
to ActiveState right now because its the flavor that's approved for 
production.  I need to minimize the height of the waves I cause because 
I'm already on fairly thin ice for choosing Catalyst/Apache/Perl instead 
of ASP/IIS/.NET for this project.  In other words my boss doesn't want 
to see any more development tool requests, he just wants the app rolled 
out already.

I still think I can bring the project home with the PPM's that are out 
there, and whatever I can get to work from CPAN that doesn't require 
complex compiling (unless this PAR thing works out).
>
>
> On 29/06/06, Nilson Santos Figueiredo Junior <acid06 at gmail.com> wrote:
>>
>> Also, unless it's something absolutely necessary, I'd suggest you
>> against deploying it in a Windows server. It's somewhat of a hassle to
>> get mod_perl or FastCGI working correctly under Windows, the best I've
>> got so far is running Catalyst under Apache::Registry, since mod_perl
>> crashes when using PerlModule directives and I can't manage to even
>> compile FastCGI and it's related Perl module and the built-in server
>> becomes really slow if you need to support IE clients directly
>> connecting thanks to the necessary -k switch.
>
> I use a binary fastcgi apache module which I downloaded from the
> fastcgi website.
> I can't remember whether I had problems compiling FCGI.pm - maybe
> that's one of the few I had to get a PPM for. If you use PPM.pm, make
> sure you add Randy Kobes' cpan mirror repository.
>
This looks positive, because strangely enough I have full control over 
whatever Apache gets installed in production.  I will definitely look 
into fastcgi if there's a problem with mod_perl (which I was planning to 
use), when I get to a point beyond running the app on the development 
server.