comment on

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

In reply to Re^2: (jptxs) Generate Config.pm for distribution in a package? by jptxs
in thread Generate Config.pm for distribution in a package? by jptxs

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


We don't bite newbies here... much
	PerlMonks