[Catalyst] OT: Use the CPAN, Luke?

J. Shirley jshirley at gmail.com
Mon Dec 1 15:36:34 GMT 2008

On Mon, Dec 1, 2008 at 1:05 AM, Marcus Ramberg <marcus at nordaaker.com> wrote:
> On Mon, Dec 1, 2008 at 3:36 AM, J. Shirley <jshirley at gmail.com> wrote:
>> That is the worst ever response to a test failure... just terrible.
>> This is a test failure at the core, because a version of a module down
>> the chain wasn't tested.
>> This is what CPAN Testers, in part, is designed to catch.  Saying
>> "they can't install a CPAN module" is an insult to the CPAN Testers
>> effort and all the toolchain authors, too.  There is a reason this
>> stuff exists, it is so that CPAN modules are widely accessible.
>> Welcome to the perl echo chamber...
> Hey, just because Jrockway is a emo who hates popularity doesn't mean we
> (the catalyst developers) don't care about installation failures. Matt has
> spent a lot of energy to make sure our dependency graph installs cleanly,
> for instance. And this issue has in fact already been resolved by the Mouse
> people, hasn't it?
> Marcus

My point with the "welcome" was that I view Catalyst as (somewhat)
outside of that echo chamber.  If ever so slightly.

The projects that care about release engineering help get out of the
echo chamber, and there needs to be more of them.  The EPO helps this,

Moose (and Mouse), Catalyst, DBIx::Class all are good examples of
release practices, in my opinion.  Certainly not flawless, but it's
getting there.

And not to dilute credit, like you said, Matt does a fantastic job and
deserves most the credit in the Catalyst + DBIC realm.  Regardless of
his perception, he is likely one of the best new user advocates

Welcome ot the circle-jerk chamber...


More information about the Catalyst mailing list