Setting up a common perl/cpan environment

Question

so I'm having a lot of fun with Perl at home for some time now.

How much more difficult do things get when you develop Perl modules (In my case it's mostly catalyst) in a team? How do we make sure we all got the same development environment (Perl/Module versions)? Simply by keeping up to date with CPAN? Do some teams setup their 'private' CPANs?

Answer 1

Using the following things should make your life easier.

check out local::lib you could easily then create a server that each member could sync these modules too.

You probably don't really want to mirror all of cpan. just the most recent modules which is why you'd use minicpan.

If you're using recommended modules in Task::Kensho then using the latest releases shouldn't be a problem as they should be surprisingly changing API on you. Basically by doing this you make sure you don't end up with your team reinventing the wheel or hopefully using 3 different modules that do the same thing.

And you want to make sure that your team uses good Perl coding practices and not the bad ones. There are a lot of bad ones. Read Perl Best Practices, remember it's just a guideline you should tune it too your team and your style.

• local::lib

• minicpan

• Task::Kensho

• Perl Best Practices