[Catalyst] Bug in Catalyst::View::Mason on CPAN but not SVN

[Alex Kavanagh]

At Thu, 22 Dec 2005 00:55:56 +0000,
Matt S Trout wrote:
> 
> On Wed, Dec 21, 2005 at 06:08:45PM +0000, Alex Kavanagh wrote:
> > Hi
> > 
> > I'm not too sure who to send this to, but there is a bug on he CPAN
> > version of Catalyst::View::Mason at line 121:
> > 
> >     121         $c->errors($error);
> > 
> > (should be $c->error($error); )
> > 
> > It IS fixed on SVN and is showing as 4 months old.
> > 
> > I wondering:
> > 
> > 1. Should I be using the SVN modules to do development (and how do I get it)?
> > 2. How often does the CPAN get updated?
> > 3. Are these stupid questions?
> > 
> > I guess things are in a state of flux, but this is such a simple bug
> > (and its being fixed) that I wonder how it gets out on to CPAN?
> 
> The latest CPAN version of this module (0.08) does
> 
>     if ( my $error = $@ ) {
>         chomp $error;
>         $error = qq/Couldn't render component "$component_path" - error was "$error"/;
>         $c->log->error($error);
>         $c->error($error);
>         return 0;
>     }
> 
> I'm not sure what you're problem is ...

Strange indeed.  Somehow I'd managed to get the 0.06 version off CPAN
when I installed Catalyst.  As I'm  new to Catalyst it was probably
something to do with installing Catalyst::Bundle first and then
finding out that I was supposed to install Task::Catalyst and the
older module had already been installed.

I've just updated it (and a few other Catalyst related modules) from
CPAN and all is fine.

If Catalyst::Bundle is not the way to go can it be removed from CPAN
or is that 'not the done thing', as it confused me?

Thanks for everybody's help with this.

Regards
Alex.