[Catalyst] How to use local::lib

Tobias Kremer tobias.kremer at gmail.com
Tue Jun 23 08:41:16 GMT 2009

On Tue, Jun 23, 2009 at 10:26 AM, Tomas Doran<bobtfish at bobtfish.net> wrote:
> I think you need a better separation between development and staging. If
> you're not running something production like in staging, then IMO you're
> really screwed.

Actually, we do :)

> Developers can then use what they like (and whatever OS/versions of modules)
> they want, if they want to install the app locally, but that's unsupported.
> I'd also make a 'production like' (i.e. same OS) vmware machine available
> with the 'standard' dependencies - all of your developers should be given
> enough horsepower to run vmware, problem solved.

Yes, that'd be possible. Nevertheless, it would be nice if you could
bring up a new development box with "make installdeps" that "just
works" because it has the right module versions installed and not some
new, probably incompatible version.

>> By the way: Would it theoretically be possible to install specific
>> versions of a CPAN distribution? Is there possibly already work
>> underway to achieve this? I think that this would really solve a lot
>> of deployment trouble ...
> Erm, it's already practically possible. You just need to ask the CPAN shell
> for a specific revision.

Cool, but what I really meant to ask was: Is it possible to require a
specific version in your Makefile.PL and have only this version
installed during "make installdeps"? :) This would possibly solve most
of the CPAN-related deployment problems.

> At work I debian package everything. But you're still going to make one
> package per dependency per platform.
> That's a lot of work.. And it totally precludes having different
> applications with different versions of the same module on the same machine.

I tried that with Catalyst::Runtime a couple of weeks ago and it still hurts :)

Thanks for your help!


More information about the Catalyst mailing list