*standard first time poster's apologies here*

Would someone please help me find PM's documentation on "how to support a network production environment while doing code changes to multiple custom packages used in common across several scripts"?

I'm not talking about the library (CVS) issues, but the roll-out of a change to a custom package while dependent scripts and packages are in use.

Is there a technique somewhere that will help me make my changes in one directory (and break things without breaking production), then move the changed code to a pre-production directory so beta testers can see it before it goes into production?

I am selfishing trying to avoid the error-prone alteration of "use lib proddir;" lines for each script that has dependencies on packages that could exist at prod, pre-prod or dev...

THANKS!

Readmore

I support a few perl apps for a large network production environment. My apps employ the use of standard packages and some custom packages of my own.

The perl scripts are kept in a commom tool location that all network users have access to. My custom packages are kept in a visible location that isn't in the standard @INC. I could perhaps change @INC, but it is already wastefully full and I'm not a sysadmin and sadly it wouldn't help me meet all requirements either.

To reach my packages, each script has a "use lib prodlib;" line to help them resolve "use CustomPackage;" statements.

I thought I had a solution when I just added after the "use lib prodlib;" line another "use lib protectedlib;" line placing a search through my own protected directory first (unreadable to anyone but me). This helped me do development on a single package that I can see, but users can't see. But woe, this doesn't help me promote changes to a "beta" level so that a few others can test a soon-to-be-production level.

My next thought was to add "YAUL" statment between my protected development library directory and the production library directory that searched a path through each user's $ENV{HOME}/preprod directory. This way, any user wanting to try out pre-production code could place a symlink to the pre-prod dir in their own home. When the prod scripts executed, suddenly the pre-prod packages would be found before the prod packages.

I trust the monks who have passed this way before know a better solution-- please accept my gratitude in advance for your patient instruction.

In reply to Supporting a production environment by jeb6kids

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.