in reply to How do manage your Perl application development, build, and deployment?

I've found the old unix maxim of small tools that do one job and do it well is a good one to keep in mind. A large "solution" isn't going to do exactly what you want. Instead a collection of solutions of the sub-problems of your task is more manageable. Then you can tie them together into your overarching solution.

In other words, a not-quite-great-but-good-enough solution may be the best there is.

--Pileofrogs

  • Comment on Re: How do manage your Perl application development, build, and deployment?

Replies are listed 'Best First'.
Re^2: How do manage your Perl application development, build, and deployment?
by TGI (Parson) on Mar 18, 2009 at 16:58 UTC

    I too find this design philosophy beneficial.

    Which tools do you use? How do you put them together?


    TGI says moo

      I use git, Module::Build and Module::Starter. I have a home-brew system for distributing the libs to my various machines. None of these are great or optimum, but it works.

      My needs are pretty simple though. I only have one OS, I don't need multiple versions of anything, I work alone, I only work on small projects.