[Catalyst] Is it normal to have lots of trouble installing catalyst?

[Christopher H. Laco]

apv wrote:
> On the heels of that.
> 
> All the problems being talked about are prerequisite related
> and some just from the complexity of the prerequisite chains.
> I had, mostly, the same problems on Darwin as I had on a shared
> DreamHost account with Linux. Though there were Catalyst
> induced problems just a couple versions ago from the conflicting
> build stuff (I think Matt fixed it in 5.61?) which is the only build
> experience some have had.
> 
> I just upgraded to 5.64 an hour ago and was forced to install
> 3 new modules--including Spiffy?--to upgrade to the required
> version of YAML. Another 2 or 3 new requirements every other

Spiffy? That doesn't seem right at all. 0.55+ doesn't have SPiffy as a
meta/makefile requirement at all.

> release is playing chicken with your users. There have been
> about 50 (I think) added since I first installed Catalyst just a
> couple of months ago.
> 
> So, the main point for me is that Catalyst is getting big
> and adding dependencies to it should not be a casual matter.
> If anything, I'd love to see them trimmed down whenever
> the chance presents. The cleaner and smaller the core
> can stay, the better for everyone who uses Catalyst.
> 
> -Ashley

On this point I have to agree. Without much detailed thought, every time
an update has come out between 5.56/5.64, I always leave the upgrade
experience with one single first impression: Why is so much changing so
fast.

I understand things change, and usually for the good, but for a while
now, I've been left with a lack of faith about upgrades being bug fixes
vs. 10 new/changed features for every minor point release.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
Url : http://lists.rawmode.org/pipermail/catalyst/attachments/20060208/df3f5148/signature.pgp