in reply to Catalyst broken after update?

Friday evening I updated Catalyst to version 5.33 through the use of the ppm command "upgrade".
Don't do that (its a pure-perl module). Read A guide to installing modules and run the test suite. Also read the Changes file.

On the other hand if its looking for Apache2, you must've installed mod_perl2 ... visit http://perl.apache.org and look for the win32 guide.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re^2: Catalyst broken after update?
by CountZero (Bishop) on Aug 21, 2005 at 20:09 UTC
    Well, I did a general upgrade and it upgraded Catalyst too (and a bunch of other modules). Serves me right for always wanting to be the first on the block with the newest modules (and not doing a general back-up beforehand). In the end (see "Update 3" on the original node) it had nothing to do with the upgrade, but all with a line in my application code that got commented out.

    CountZero

    "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

[reply]

In Section Seekers of Perl Wisdom