I use packages to manage all of my software, and that includes the perl programs I maintain. This doesn't magically let you have different development and production environments, but it does allow you to replicate your dev env with minimal pain (imho).

My testing and production environments are updated using red carpet, although other solutions could be used instead (using apt, for example). On my development environment, though, I use the software I maintain unpackaged (but I use packages for its dependencies). So the only real difference is that in the dev env's @INC needs to include my development modules. I accomplish this with a little hack:

use FindBin;
use lib "$FindBin::RealBin/../lib";

[download]

That means that @INC will include prefix/lib (e.g., /usr/lib) on a production system. If that's a problem, then you can comment out those lines before packaging the software for production use.

This solution is more or less limited (in practice, not in nature), to systems with solid package management that can do dependency resolution. Meaning, if you plan to deploy software on e.g., Windows, then you'll need an additional package management layer, or a different solution.

I'd be very interested in any comments, suggestions, or other working solutions other people might have!

In reply to Re: Machine replication by v_thunder
in thread Machine replication by set_uk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.