That still means you have to run that, and let it sit and update many modules. They all stop and ask questions and need attention. Once you’ve updated half of Catalyst, you have to go back and check that everything else that depends on it (since you’re installing globally instead of in local::lib) still works.

One good thing is that the Catalyst guys are really careful with updates. I have yet to have a Catalyst update break a working app.

I understand that these projects are quick moving. I recommend using a Makefile.PL to track versions, along with local::lib to manage your dependencies. That way you don’t get lost in the confusion.

Hm. I’m not seeing that. In the Intro it says, “You can obtain the code for all the tutorial examples from the catalyst subversion repository” — which I did, and … there it is in each chapter. Ah. I was looking for something in the top level. Well. I learn something new every day…

I would agree (and am thrilled) that “the Catalyst guys are really careful with updates.” It’s one of the few Open Source projects I’m willing to just keep current without too much worry. (Gold Star to them.)

That still means you have to run that, and let it sit and update many modules. They all stop and ask questions and need attention. Once you’ve updated half of Catalyst, you have to go back and check that everything else that depends on it (since you’re installing globally instead of in local::lib) still works.

One good thing is that the Catalyst guys are really careful with updates. I have yet to have a Catalyst update break a working app.

I really wasn’t thinking I needed to keep a list of dependencies for the Catalyst tutorial. I don’t think the tutorial can avoid this, though. It should be one of the most up-to-date items in the documentation set, right? Maybe the tutorial download should come with its own Makefile.PL, so folks can just run that and get the current software they’ll need.

I’m trying to avoid using local::lib, as I am working on four very different machines. My main development environment for these projects is a remote machine I SSH to (SuSE), but I also work on or from my desktop (WinXP), a “throw away” laptop (WinXP), and a tiny laptop (SuSE).

Trying to keep each environment up-to-date (which would require each have a local CPAN mirror ((which would need to be kept up-to-date, so I would either need to update that before I started work, or each machine would need to be left running on the network so it could do that automatically when I wasn’t using it)) or to download each update over the ‘net as necessary) sounds like much more trouble than it’s worth.

I understand that these projects are quick moving. I recommend using a Makefile.PL to track versions, along with local::lib to manage your dependencies. That way you don’t get lost in the confusion.