Which modules do you "allow" yourself to use for production?

Toddy endontoddy at googlemail.com
Tue Jul 23 10:38:22 BST 2013

Once you have decided what modules you need. Don't rely on installing them
all directly from CPAN. Keep the exact versions of the module you're using
in either your own CPAN mirror or packaged with your self-brewed Perl to
simplify consistency across all of your environments.

On 22 July 2013 23:35, Dave Hodgkinson <davehodg at gmail.com> wrote:

> Don't use system Perl. Brew your own and make it part of the app.
> Sent from my iPhone
> On 22 Jul 2013, at 23:04, Pierre M <piemas25 at gmail.com> wrote:
> > Thank you, all. That's very good advice.
> >
> > Yup, the main thing is to make money before it runs out. Abigail, your
> > comments to Ovid's blog post (about testing) were just what i needed to
> > read at the time, on this subject.
> >
> > Summary of the ideas so far:
> > - it depends on the size of the project
> > - don't re-invent the wheel
> > - "dependency hell" will become visible when i will want to upgrade
> stuff.
> > So be careful from the start, and find a good enough balance.
> > - don't spend too much time getting it perfect: start writing code

More information about the london.pm mailing list