[Catalyst] install Task::Catalyst with ActivePerl 5.8.8.817

[Wade.Stuart at fallon.com]

catalyst-bounces at lists.rawmode.org wrote on 04/26/2006 03:57:19 PM:

> At 02:50 PM 4/26/2006, Will Smith wrote:
> Hi,
> I am upgrading my cat app from an old version to the latest version
> from cpan. I'm running cat app on Windows 2000. I have the
> ActivePerl 5.8.8.817 installed. I have nmake in the Perl\bin
> directory. And this is the error that I got:
> ---------------------
> CPAN: Storable loaded ok
> Going to read C:\Perl\cpan\Metadata
>   Database was generated on Wed, 26 Apr 2006 09:34:31 GMT
> Running install for module Task::Catalyst
> Running make for S/SR/SRI/Task-Catalyst-1.70.tar.gz
> <snip>
>   CPAN.pm: Going to build S/SR/SRI/Task-Catalyst-1.70.tar.gz
> Undefined subroutine &ActivePerl::Config::find_prog called at C:
> /Perl/site/lib/A
> ctivePerl/Config.pm line 70.
> Compilation failed in require at C:/Perl/lib/ExtUtils/MakeMaker.pm line
7.
> <snip>

> -----------
>
> Would someone show me why I get this error.  Or if this error has
> been pointed out before, please give the link to the thread. Thank
> you for your help.
> Will
>
> Please see the descriptions in
>     http://bugs.activestate.com/show_bug.cgi?id=45338
> Also discussed in list postings here on 3/15
>
> Once I did the xcopy overwrite of the Task-Catalyst's copy of
> Module::Install, things progressed well with Task-Catalyst up to a point.
>
> Because of error messages, I thought had to use ppm3 to install
> Test::WWW::Mechanize, but still had problems until I used ppm3 to
> install Test::Longstring, which is apparently an undocumented
> dependency for Test-WWW-Mechanize-Catalyst.
>
> Then I got hung up on a dependency for Template-Timer, which I
> installed using ppm3.
>
> Then I got hung up by other confusions ... and work.
>
> Anyway, wanted to note the Module-Install glitch, wish ALOUD that
> Task-Catalyst-0.71 is forthcoming, and wonder about the unnoted
> Test-Longstring  dependency.

Of course it has also been noted on this list multiple times 5.8.8 is
pretty "iffy",  there are many weird things afoot in that release -- most
here are sticking with 5.8.7 or 5.8.5 until those issues get resolved.