Config.pm seems to be more subtle than that. It makes distinctions between different shades of AIX (different kernel settings, paramters, compilers, etc.) that the larger software package we distribute does not. In other words, Config.pm demands a greater level of specificty than any other part of our software package. So even if we generated a Config.pm for each server we build on in our labs, that would not cover the diversity of servers our software may eventually be installed on. I hope that helps clarify.
It's starting to seem that there is no solution other than a brute force one (genrating a great deal of possible Config.pm files and putting them all in a directory structure that's addressed dynamically based on local configuration).
We speak the way we breathe. --Fugazi
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||