In our development env, we have, for each release, a "version" of perl that is compliled to know about that version, and the @INC path associated with that. Now, going on release 4.0, and many intervening releases in between, it's getting unwieldy to have to change the interpreter calls in all our perl code as we spin a new release.
What we'd like to do is to link to the current release as /usr/local/OurPerl/bin/perl, but provide the ability to override that (for testing, bug fixing, sustaining maintenance, etc.) via a user ENV variable, say TEST_PERLROOT.
I've just started to muck about with some ideas, but each seems messier than the last.
Anyone else have to solve this problem, or have ideas?
Thoughts much appreciated,
- bill
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.