[Catalyst] IMPORTANT: Catalyst::Plugin::FormBuilder obsoleted by ::Controller::FormBuilder

Juan Camacho jc5826 at gmail.com
Wed Jan 3 01:57:50 GMT 2007


On 1/2/07, David Morel <david.morel at amakuru.net> wrote:
>
> Le 3 janv. 07 à 00:29, Nilson Santos Figueiredo Junior a écrit :
>
> > On 1/2/07, Jonathan Rockway <jon at jrock.us> wrote:
> >> Incidentally, I wrote the chapter of my book on FormBuilder the day
> >> before the Controller was released :)  However, updating the chapter
> >> only took about 30 seconds... so no excuses!
> >
> > I find it somewhat worrying that the first book to be published about
> > Catalyst has a chapter about a module that currently doesn't install
> > cleanly under Windows.
> >
> > Actually, I have no idea how Test::WWW::Mechanize tests manage to
> > crash perl under Windows on almost all test cases.
>
> Pardon me everyone, but this is getting old. If T:W:M fails to build
> on winblows, the thing to do is post a bug report on rt.cpan.org (and
> dig in the errors). This has nothing to do with Catalyst or
> C:C:FormBuilder.
>

I agree and the following response also belongs elsewhere.

I was curious about Perl on Windows and managed to install Mechanize,
etc on the latest version of ActivePerl. I'm surprised how far Windows
Perl has come BTW.

First, I pointed my PPM repository to
http://theoryx5.uwinnipeg.ca/ppms/package.lst and tried to install
Test-WWW-Mechanize-Catalyst, but got the following error:

ERROR: File conflict; package Catalyst-Runtime already provide
C:/Perl/html/bin/catalyst.html

That's because PPM tries to install Catalyst which is listed
separately and I had already installed Catalyst-Runtime.  Obviously,
PPM doesn't know the difference between the old and new version of
Catalyst.

So I did the following: a) removed Catalyst-Runtime, b) installed
Catalyst, c) installed Mechanize, d) removed Catalyst and e) then
finally re-installed Catalyst-Runtime.  Pretty stupid, I know.

Finally I used the CPAN command line to install C-C-FormBuilder,
fixed an nmake "Undefined UpdateHTML_blib" error as described at
http://support.activestate.com/forum-topic/nmake-of-packages-resulti
and got it to install fine -- all test passed.

So, it seems with a little bit of common sense and digging around, you
could get it installed on Windows in about 30 minutes without any
prior experience in that sort of stuff.



More information about the Catalyst mailing list